pycodestyle icon indicating copy to clipboard operation
pycodestyle copied to clipboard

πŸŽ› A Svelte library for building dynamic, infinitely customizable node-based user interfaces and flowcharts

Results 211 pycodestyle issues
Sort by recently updated
recently updated
newest added

quoting PEP 8 : "_Surround top-level function and class definitions with two blank lines._ _Method definitions inside a class are surrounded by a single blank line._ _Extra blank lines may...

Cells are separated by lines starting with: #%% (standard cell separator) # %% (standard cell separator, when file has been edited with Eclipse) # (IPython notebook cell separator) But `pycodestyle`...

Adding `# noqa`s as below has no effect on `pycodestyle`, which still complains about `E501` violation. ``` # noqa x = "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", \ "b" # noqa ``` (using long string...

The python formatter `black` will occasionally decide to put a binary operator by itself on a line ([example](https://github.com/tornadoweb/tornado/blob/715ef05682c354e704c7621bfd1a28ad9a52e0d6/tornado/http1connection.py#L406)). This triggers the newly-added W504 warning. I believe that W504 (and W503,...

It looks like unicode combining diacritics are counted as full characters, which causes `E501` to fire, even when it is visually less than 79 characters: ```python text = ['ся́ду', 'Ρ‚Π²Ρ‘Ρ€Π΄Ρ‹ΠΉ',...

Currently, one-liner classes (`class Foo: pass` or for example more realistically `class T(Enum): a, b, c = range(3)`) trigger E701 ("multiple statements on one line (colon)"). I would suggest moving...

``` $ cat foo.py foo = lambda x: x bar = (lambda x: x) $ pycodestyle foo.py foo.py:1:1: E731 do not assign a lambda expression, use a def ``` The...

:wave: I'm scoping implementing: warn on unused `noqa` comments (for flake8) and I've noticed a problem with my initial approach, the E402 error can be suppressed by a `noqa` comment...

E721 is there to prevent `type(3) == int` in favour of `isinstance(3, int)`. Thats fine. But it also raises an error for code like `type(a) == type(b)`. This is good...

Example: ```python assert x % None == tuple(1) ``` Results in "comparison to None should be 'if cond is None:' [E711]" even though the expression on the left is unknowable...