forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Log indicates failure but .venv
folder has been created
#19889
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
area-environments
Features relating to handling interpreter environments
bug
Issue identified by VS Code Team member as probable bug
needs PR
Ready to be worked on
verified
Verification succeeded
Milestone
Comments
.venv
folder has been created.venv
folder has been created
@jrieken In this case the environment is created and can be used. But packages cannot be installed in it. We will attempt to discover this earlier and try to fail the whole env creation process. |
eleanorjboyd
pushed a commit
to eleanorjboyd/vscode-python
that referenced
this issue
Oct 4, 2022
Closes microsoft#19889 Closes microsoft#19890 Closes microsoft#19891 Closes microsoft#19894 Closes microsoft#19897 Closes microsoft#19852 Closes microsoft#19851 Closes microsoft#19838 Closes microsoft#19916 Closes microsoft#19917
What's the best way to verify this? |
You have to force a failure in |
wesm
pushed a commit
to posit-dev/positron
that referenced
this issue
Mar 28, 2024
Closes microsoft/vscode-python#19889 Closes microsoft/vscode-python#19890 Closes microsoft/vscode-python#19891 Closes microsoft/vscode-python#19894 Closes microsoft/vscode-python#19897 Closes microsoft/vscode-python#19852 Closes microsoft/vscode-python#19851 Closes microsoft/vscode-python#19838 Closes microsoft/vscode-python#19916 Closes microsoft/vscode-python#19917
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-environments
Features relating to handling interpreter environments
bug
Issue identified by VS Code Team member as probable bug
needs PR
Ready to be worked on
verified
Verification succeeded
Testing #19883
I am no expert in this and don't really know what success means but I went through the "create env > venv" flow, everything seemed file but checking the logs it reads:
Now I am confused I don't know if this was successful or not
The text was updated successfully, but these errors were encountered: