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.

Error running flake 8

See original GitHub issue

Hi, without changing anything (intentionally at least) I have an error when opening Atom:

[Linter] Error running Flake8 Error: /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/pep8.py:102: FutureWarning: Possible nested set at position 1
  EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')
    at ChildProcess.<anonymous> (/Users/xxxxx/.atom/packages/linter-flake8/node_modules/sb-exec/lib/index.js:56:20)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:885:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

Studying previous posts didn’t help, so I’m posting my own issue.

Issue Analytics

State:
Created 6 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

cclausscommented, Jul 1, 2018

Why is this issue closed?

Upgrading to production Python 3.7.0 on Mac OSX disables the current version of AtomLinter/linter-flake8 (with an error message every time I type a character) and I see no workaround in this issue?

The root cause is visible on the command line in the current production flake8 running on the current production Python on the current production Mac OSX…

$ flake8 --version

/usr/local/lib/python3.7/site-packages/pycodestyle.py:113: FutureWarning: Possible nested set at position 1
  EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')

3.5.0 (mccabe: 0.6.1, pycodestyle: 2.3.1, pyflakes: 1.6.0) CPython 3.7.0 on Darwin

The problem is that AtomLinter/linter-flake8 is choking on this pycodestyle warning message instead of eating it and moving on to do what it is supposed to do.

0reactions

declantraynorcommented, Jul 5, 2018

@cclauss See my comment here for a temporary workaround.