You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 7, 2023. It is now read-only.
When specifying the Pep8 Executable Path using the $PROJECT variable, the following error appears:
Error: spawn $PROJECT/venv/bin/pep8 ENOENT
at exports._errnoException (util.js:890:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
at onErrorNT (internal/child_process.js:348:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
It works fine when specifying the absolute path to that pep8 executable and when starting Atom from within the virtual environment, but I would prefer to use the $PROJECT variable (as is done in the linter-flake8 package for instance).
The text was updated successfully, but these errors were encountered:
When specifying the Pep8 Executable Path using the $PROJECT variable, the following error appears:
It works fine when specifying the absolute path to that pep8 executable and when starting Atom from within the virtual environment, but I would prefer to use the $PROJECT variable (as is done in the linter-flake8 package for instance).
The text was updated successfully, but these errors were encountered: