Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Pyolite is always the selected kernel for new notebooks #12236

Closed
roblourens opened this issue Nov 30, 2022 · 4 comments
Closed

Pyolite is always the selected kernel for new notebooks #12236

roblourens opened this issue Nov 30, 2022 · 4 comments
Assignees
@DonJayamanne
Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone
November 2022

Comments

@roblourens
Copy link
Member

Testing #11963

  • Install Pyolite
  • Use some other kernels in your notebooks
  • Run "Create new jupyter notebook"
  • Pyolite is the autoselected kernel even though I've never actually used it
@DonJayamanne
Copy link
Contributor

This is a regression.
In new notebooks Jupyter extension is no longer providing a preferred kernel.

@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug kernel-picker labels Nov 30, 2022
@DonJayamanne DonJayamanne added this to the November 2022 milestone Nov 30, 2022
@rebornix rebornix removed their assignment Dec 1, 2022
@rebornix
Copy link
Member

rebornix commented Dec 1, 2022

Fixed via b2ebc82

@rebornix rebornix added the author-verification-requested Issues potentially verifiable by issue author label Dec 1, 2022
@DonJayamanne
Copy link
Contributor

to be verified

@roblourens roblourens added the verified Verification succeeded label Dec 2, 2022
@roblourens
Copy link
Member Author

roblourens commented Dec 2, 2022 •
edited
Loading

We discussed this in the notebook sync. Verified as-is, but there is still some possible randomness here. I think the decision was for it to only autoselect kernels that are in the mru. Whoever is responsible for that, please open an issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DonJayamanne DonJayamanne

Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Milestone
November 2022
Development

No branches or pull requests
3 participants
@roblourens @rebornix @DonJayamanne