Skip to content

Conversation

blink1073
Copy link
Contributor

No description provided.

@blink1073 blink1073 changed the title Allow a session to connect to an existing kernel [WIP] Allow a session to connect to an existing kernel Mar 21, 2016
@blink1073 blink1073 changed the title [WIP] Allow a session to connect to an existing kernel Allow a session to connect to an existing kernel Mar 21, 2016
@blink1073
Copy link
Contributor Author

This is ready for review. I allowed it to use the kernel name if the kernel id is not active, for compatibility with the existing notebook.

@minrk minrk added this to the 5.0 milestone Mar 21, 2016
minrk added a commit that referenced this pull request Mar 21, 2016
Allow a session to connect to an existing kernel
@minrk minrk merged commit 1c7bc21 into jupyter:master Mar 21, 2016
@minrk
Copy link
Member

minrk commented Mar 21, 2016

Nice! And I think we do want to keep the new-kernel if one doesn't exist, since that should still be the majority use case.

minrk added a commit to minrk/notebook that referenced this pull request Apr 13, 2016
@minrk minrk modified the milestones: 4.2, 5.0 Apr 13, 2016
yuvipanda pushed a commit to yuvipanda/notebook that referenced this pull request Jul 26, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants