-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Feedback from Jupyter notebook extension early adopters #113245
Comments
Im on Version: 1.53.0-insider |
Need more info for the following to understand the issue:
Info related to some of the issues reported above:
|
@rebornix Additional feedback has come in since this issue was created and want to make sure we are also capturing the cell execution hanging and the interrupt cell execution also not working |
Created issue but realized it was mentioned here.
|
@rebornix Can the vscode team please reconsider menu contributions? There are lots of issues with complaints about users being forced to have jupyter installed with the python extension, and msft's python/jupyter extension team ignores feedback and users complaints and quickly shuts down any discussion unless it's from a vscode team member. |
@rebornix I think this issue is a bit outdated, leaving for you to decide if you want to keep it open. |
We have received hundreds of good feedbacks from early adopters of the Jupyter extension using native notebook support. The clean UX, seamless integration with VS Code ecosystem and improved performance are mostly loved. However we are also seeing bugs and UX issues users are struggling with. Here I tried to compile the feedbacks into issues so we can track where we are with them.
Bugs & UX improvements
Core
Jupyter
Feature Requests
Core
Jupyter
The text was updated successfully, but these errors were encountered: