-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a setting for the path to pipenv #2139
Comments
Thank you for taking the time to send us this report! We will attempt to reproduce the issue and prioritize accordingly. That said, I have experienced this as well with Pipenv virtual environment while busy doing other things. I should be able to reproduce fairly simply. |
This is currently by design as pipenv is a CLI app and so we don't look for it installed in a virtual environment (its ability to be executed with |
May I suggest you to use the Because that command prompt indeed have a pipenv executable, as its PATH is changed. Or, maybe, use the "Python Command Prompt", as it does have PATH changed too. In fact, the only PATH that remained inaltered was the one used by VS Code Python extension, trying to find pipenv. |
Duplicate of #978 |
Environment data
Actual behavior
Open workspace folder, and receives Python extension notification:
Workspace contains pipfile but attempt to run 'pipenv --venv' failed with 'spawn pipenv ENOENT'. Make sure pipenv is on the PATH.
On developer tools, process.env.Path does not include anything related to python (neither from anaconda nor from my virtual environment)
Expected behavior
Open workspace folder, have VS Code activate my virtual environment as default for all python related interactions (intellisense, terminal, go_to_function, ...), as it has found my Pipefile
Steps to reproduce:
"Path": "C:\\WINDOWS\\system32;.........;C:\\...\\VSCodeInsiders\\bin"
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)Regarding python settings, only my usersettings json have relevant configuration:
I tried to select a Python interpreter, i.e., setting the
python.pythonPath
variable to either Anaconda or the virtualenv python.exe, but neither of those solved the issue of not being able to run Pipenv.The
terminal.integrated.shellArgs.windows
solved at least the issue that I was not being able to open terminal with anaconda configuration.Before that setting, if I opened the terminal, I would have the error:
activate is not a terminal command....
(something similar to that)So, I forced VS Code to run the activation of anaconda, so as to populate the PATH for terminal.
My windows default PATH, indeed, does not include anything related to anaconda. On my windows Terminal, I have to first run the Activate.bat command, so as to include relevant folders on PATH before being able to run "pipenv".
The text was updated successfully, but these errors were encountered: