-
Notifications
You must be signed in to change notification settings - Fork 293
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
Do not automatically trigger environment discovery at startup #12719
Comments
DonJayamanne
added
debt
Code quality issues
notebook-kernel-picker
and removed
debt
Code quality issues
labels
Feb 2, 2023
FYI we have been recommending folks to disable Jupyter extension for related issues: microsoft/vscode-python#20446 (comment) |
@DonJayamanne Any status on prioritizing this? |
Look at my comment here: microsoft/vscode-python#21010 (comment) |
DonJayamanne
added
the
under-discussion
Issue is under discussion for relevance, priority, approach
label
Jun 6, 2023
This was referenced Jul 13, 2023
DonJayamanne
added
debt
Code quality issues
and removed
feature-request
Request for new features or functionality
under-discussion
Issue is under discussion for relevance, priority, approach
labels
Dec 1, 2023
Done |
This shuold now be done, #15261 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Already brought it up with @DonJayamanne but opening this issue to track it.
I understand with the current design of kernel picker this is not possible. However, with the new design discovery can be triggered when the list is opened instead, so this can be avoided.
The text was updated successfully, but these errors were encountered: