Skip to content

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

Merged
merged 1 commit into from
Dec 11, 2015

Conversation

SylvainCorlay
Copy link
Member

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.

@SylvainCorlay
Copy link
Member Author

I probably closed the earlier PR accidentally.

@minrk
Copy link
Contributor

minrk commented Oct 14, 2015

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 Kernel.comm_info if it's not already available on Kernel. But waiting for notebook-4.1 is fine, too.

@SylvainCorlay SylvainCorlay force-pushed the comm_info branch 3 times, most recently from f78a957 to 06ed09f Compare October 20, 2015 14:19
@jdfreder jdfreder added this to the 4.2 milestone Oct 22, 2015
@jdfreder jdfreder modified the milestones: 4.2, 5.0 Oct 30, 2015
@SylvainCorlay SylvainCorlay force-pushed the comm_info branch 4 times, most recently from e88f38c to 4bdce8c Compare November 30, 2015 17:00
@SylvainCorlay
Copy link
Member Author

@jdfreder I rebased an now require notebook 4.1beta.

'traitlets',
'notebook',
'notebook>=4.1.0b1',
Copy link
Contributor

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?

Copy link
Member Author

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet

jdfreder added a commit that referenced this pull request Dec 11, 2015
Remove workaround for comm_info message
@jdfreder jdfreder merged commit decff87 into jupyter-widgets:master Dec 11, 2015
@SylvainCorlay SylvainCorlay deleted the comm_info branch December 11, 2015 20:54
@github-actions github-actions bot added the resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Feb 26, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature request kernel authors beware resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants