-
Notifications
You must be signed in to change notification settings - Fork 1.2k
"Create environment" error message isn't helpful #20297
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
Comments
We added modal error for some cases. @luabud Should we switch to error notification only in all cases? |
Yeah I think that's a good idea. It's not a blocking error (in a sense that if you end up choosing a different environment you can keep going), so I vote for using error notifications in all cases. @cwebster-99 -- what do you think? |
I think switching to only showing error notifications makes sense for this scenario and reduces "clutter" on the screen. Are we able to add more information to the error notification (i.e. add information from the modal notification to the error notification) so it is more actionable for the user without them having to show output? |
I believe #21896 fixed this. Errors are now reported only through a notification, where you can either check the output or select a different interpreter: |
Testing microsoft/vscode-jupyter#11963
I just ran "Create environment" with the global python iterpreter, I can't remember how I set it up but I suppose it doesn't have pip available. Also there should not be 2 error messages
The text was updated successfully, but these errors were encountered: