forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Pipenv not activated and pipenv command not used #14829
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
Labels
bug
Issue identified by VS Code Team member as probable bug
Comments
Possibly related to #14828 |
Should be fixed along with #12011 |
I closed this as dup of that. We only need to track it in one place. |
Just saw your comment on 12011. Thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Environment data
python.languageServer
setting: Jedi or PylanceExpected behaviour
When working in a Pipenv environment, the Pipenv virtual environment would be activated and
pipenv install
would be used for any installations instead of pipActual behaviour
The virtual environment is activated but Pipenv is not and pipenv commands are not used, only pip commands.
Steps to reproduce:
pipenv install
./.venv/bin/python
)pip install -U package_name
Logs
Output from Terminal
Output for
Python
in theOutput
panelThe text was updated successfully, but these errors were encountered: