-
Notifications
You must be signed in to change notification settings - Fork 949
Remove workaround for comm_info message #175
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
Conversation
I probably closed the earlier PR accidentally. |
e480260
to
5259811
Compare
Just noting that this doesn't actually require the jupyter_client patch, since the messages go directly to ipykernel. If you wanted it to work on the notebook today, you could add a backward-compat shim to define |
f78a957
to
06ed09f
Compare
e88f38c
to
4bdce8c
Compare
4bdce8c
to
b6440b4
Compare
@jdfreder I rebased an now require notebook 4.1beta. |
'traitlets', | ||
'notebook', | ||
'notebook>=4.1.0b1', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My python packaging knowledge to too weak -- will we have to change this when 4.1.0 final is released?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. If you look just above, we had ipython>=4.0.0dev0
for a long time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sweet
Remove workaround for comm_info message
This depends on versions of jupyter_client, ipykernel and notebook including the following changes
jupyter/jupyter_client#34 merged
ipython/ipykernel#25 merged
jupyter/notebook#166, merged
This now only requires the notebook 4.1 to be released.