question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stops working after upgrading flake8 from 2.5.5 to 2.6.0

See original GitHub issue

linter-flake8 has stopped working after I upgraded flake8 from 2.5.5 to 2.6.0 using pip. I am not sure if this is a bug with linter-flake8 or flake8 though. If it is the latter, please let me know so that I can file a bug report with flake8 instead.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
edwinkslcommented, Jun 23, 2016

It looks like this has been fixed after the latest update to linter to 1.11.14. Please feel free to close this issue, thanks!

0reactions
edwinkslcommented, Jun 17, 2016

flake8 --version gives 2.6.0 (pycodestyle: 2.0.0, pyflakes: 1.2.3, mccabe: 0.5.0, flake8-docstrings: 0.2.7, pep257: 0.7.0, hacking.core: 0.0.1, ProxyChecker: 0.0.1) CPython 3.5.1+ on Linux.

Without commenting out the definition for b, flake8 foo.py gives:

foo.py:2:80: E501 line too long (88 > 79 characters)
foo.py:5:7: E901 SyntaxError: invalid syntax

Commenting out, flake8 foo.py gives:

foo.py:1:1: D100 Missing docstring in public module
foo.py:1:1: D103 Missing docstring in public function
foo.py:2:80: E501 line too long (88 > 79 characters)

I also did the same test with Python 2.7.11. In Atom, running the same code without commenting out the definition for b gives

Error E501 — line too long (88 > 79 characters) at line 2 col 80
Error E901 — SyntaxError: invalid syntax at line 5 col 7

while commenting it out gives

Error E501 — line too long (88 > 79 characters) at line 2 col 80
Warning D100 — Missing docstring in public module at line 1 col 1

It seems the D100 warning should also have appeared when the definition of b is not commented out but intriguingly, it only appears after the definition of b is commented out.

Read more comments on GitHub >

github_iconTop Results From Across the Web

5.0.0 fails with flake8 · Issue #406
When installing hacking from a wheel, it gets 4.1.0, which depends on flake8 3.8.x and flake8 3.8.x doesn't pin importlib_metadata.
Read more >
Changes — flake8 2.5.5 documentation
Bug Files excluded in a config file were not being excluded when flake8 was ... by upgrading dependencies; Fix traceback when running tests...
Read more >
flake8 2.6.0
Fix crashes with Python 3.4 by upgrading dependencies. Fix traceback when running tests with Python 2.6. Fix the setuptools command python setup.py flake8...
Read more >
flake8 Documentation
A plugin that augments the output of Flake8 when passed to flake8 ... Note: Installing Flake8 once will not install it on both...
Read more >
1377125 – python-hacking doesn't work with flake8 3.x
I've updated flake8 to 3.0.4 in rawhide, and after doing that ... Looking at hacking upstream, it seems updating flake8 was a bit...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found