-
Notifications
You must be signed in to change notification settings - Fork 276
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
Select kernel options missing when after running a jupyter notebook cell in VScode Insiders #6036
Comments
@ChandlerTayek Could you please provide the extension versions that you are using for Jupyter and Python? |
@claudiaregio Yes |
I am not able to reproduce with the same extension versions and the latest version of vs code. Version: 1.57.0-insider (user setup) |
@claudiaregio @joyceerhl Amazing that we posted the same thing at the same time. Thanks for being friendly and helpful! Love the product and I try every bit to not use something else when it isn't working as expected. |
Thanks for filing a bug and we appreciate your understanding as we work to improve the extension--we're always grateful for feedback and support from users like you 😊 |
Yeah in terms of products that I use at my job for Machine Learning, some of the features VScode Insiders provides are the best in the industry as development editors go IMO. Keep up the great work. |
Thanks @ChandlerTayek! Don't hesitate to reach out for any other feedback or feature requests! |
When creating a fresh
![image](https://user-images.githubusercontent.com/6510301/120048989-85449f80-bfcd-11eb-87f4-fd954a39c83c.png)
.ipynb
file and trying to runprint('hello world')
I get prompted to select from an empty list of kernels.Here is a list of my current available kernels on my machine:
![image](https://user-images.githubusercontent.com/6510301/120049145-f08e7180-bfcd-11eb-8aa6-f322839a99e4.png)
I have tried reinstalling the python and jupyter notebook extension for VScode with no luck.
Edit: I'm running 1.57.0-insider on Windows 10 Home
The text was updated successfully, but these errors were encountered: