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.

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

Move "New Jupyter File" (ipynb) command and implementation to VS Code core #9250

Closed
greazer opened this issue Mar 6, 2022 · 0 comments · Fixed by #9311
Closed

Move "New Jupyter File" (ipynb) command and implementation to VS Code core #9250

greazer opened this issue Mar 6, 2022 · 0 comments · Fixed by #9311
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@greazer
Copy link
Member

greazer commented Mar 6, 2022

Because VS Code core is able to read and write ipynb files without the help of the jupyter extension, it only makes sense to move the code/command that creates a new ipynb file to core as well.

Whether the Jupyter extension is recommended on creating the file, executing code, or picking a kernel will need to be resolved as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants