-
Notifications
You must be signed in to change notification settings - Fork 290
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
Ship our own Jupyter to eliminate configuration problems #1131
Comments
I think from our (Julia) point of view it would be great if this was somehow only triggered if a user is using Jupyter Notebooks with Python, i.e. if this was entirely skipped in a scenario where a user is installing the Jupyter extension to work with Julia Jupyter notebooks. We are converging on a very nice integration in julia-vscode/julia-vscode#980 that is completely zero-config, zero-install for the Julia scenario. If we could keep this Julia scenario in a state that nothing Python gets triggered or installed on a user system, that would be great. |
Closing this issue for now, as we haven't got any plans for this yet. |
We've had tons of issues related to people not having jupyter configured correctly (examples):
https://github.com/microsoft/vscode-python/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3A%22data+science%22+tornado
(as of this bug there were 18 issues just with tornado configuration).
We should ship our own jupyter to eliminate these issues. We can have the latest greatest all the time and use this to make sure we can install our own kernels.
The text was updated successfully, but these errors were encountered: