-
Notifications
You must be signed in to change notification settings - Fork 293
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
Display local and remote kernels in together in the kernel picker #8778
Labels
Milestone
Comments
DonJayamanne
added
the
bug
Issue identified by VS Code Team member as probable bug
label
Jan 23, 2022
DonJayamanne
added
testplan-item
and removed
bug
Issue identified by VS Code Team member as probable bug
labels
Jan 23, 2022
This was referenced Jan 25, 2022
FYI, there were two Create Issue links in this TPI header. I removed the one that pointed to #8489 so that all the mentions show up linked to this TPI. |
Yes |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Refs: #8489
Complexity: 4
Authors: @DonJayamanne
Create Issue
We now allow users to connect to local and remote jupyter servers within the same VS Code session.
Setup steps:
For non-conda environments use the command
python -m pip install jupyter notebook
, and for conda use the commandsconda install -c conda-forge notebook
python -m jupyter notebook
http://localhost:8888/?token=aae7097a0f2e63
)Test steps: (repeat multiple times)
Jupyter; Specify local or remote..
Existing
& enter the URl copied earlier(Remote) Jupyter Kernel
)The text was updated successfully, but these errors were encountered: