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.

Failed to spawn flake8

See original GitHub issue

Today I started receiving this error when I edit a Python file:

Failed to spawn command flake8. Make sure flake8 is installed and on your PATH
Close All
Error: spawn flake8 ENOENT
Error: spawn flake8 ENOENT
    at exports._errnoException (util.js:837:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:441:9)
    at process._tickCallback (node.js:355:17)
Failed to spawn command flake8. Make sure flake8 is installed and on your PATH
Error: spawn flake8 ENOENT
Error: spawn flake8 ENOENT
    at exports._errnoException (util.js:837:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:441:9)
    at process._tickCallback (node.js:355:17)

That pops up the console, which shows:

captura de pantalla de 2015-12-21 09-36-06

Changing the path of the executable to /usr/bin/flake8 shows the same error.

> which flake8
/usr/bin/flake8
> atom --version
1.3.1

I had to disable linter-flake8 for now. 😞

Issue Analytics

State:
Created 8 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

4reactions

danielzfranklincommented, Dec 22, 2015

I have the same error with a python file that does exist, which flake gives /usr/local/bin/flake8. I have tried restarting Atom.

1reaction

pramakucommented, Nov 21, 2017

I got the similar error when I installed flake8 package on python virtual env which is is not set in PATH(Windows), adding that directory to the PATH solved the issue.