-
Notifications
You must be signed in to change notification settings - Fork 286
-
Notifications
You must be signed in to change notification settings - Fork 286
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
Reopening: Python snippets not working with Jupyter Notebook (.ipynb) files #1850
Comments
Snippets are still something we want to support in the future but at this point, it is not high priority at the moment. |
OK, can an issue be kept open for it? Otherwise, how could it ever become a priority without the issue open-close-repeat cycle? |
Sure we can leave this open to keep track of it. |
Snippets should happen automatically when we switch to the VS code native notebook support. That's why the other bug was closed. We're never going to do this ourselves. |
@rchiodo What do you recommend for users so that we can request/track/evaluate features that may one day appear? |
For the VS code notebook implementation, you can look here: The core VS code team is implementing support for editing notebooks. Our team (the python extension) will likely be adding execution to this in our extension. Snippets should be an editor feature, so it should end up in the VS code part of the notebook implementation. |
Closing this issue, as native notebook cells are now first class VS Code text editors supporting extnsions, snippets and the like. |
As the previous issue microsoft/vscode-python#8978 has been closed and comments are restricted, reopening this issue here.
The text was updated successfully, but these errors were encountered: