Skip to content
This repository was archived by the owner on Aug 7, 2023. It is now read-only.

$PROJECT variable doesn't work #87

Closed
jvanmalder opened this issue Sep 27, 2016 · 1 comment
Closed

$PROJECT variable doesn't work #87

jvanmalder opened this issue Sep 27, 2016 · 1 comment

Comments

@jvanmalder
Copy link

jvanmalder commented Sep 27, 2016

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).

@yyovkov
Copy link

yyovkov commented Oct 5, 2016

I am also struggling to use linter-pep8 with different projects. The $PROJECT environment would solve my issues.

Arcanemagus added a commit that referenced this issue Aug 9, 2017
Add substitutions for $PROJECT and $PROJECT_NAME, largely copied and
modified from `linter-flake8`'s implementation.

Fixes #87.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants