-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Yank ipykernel 6.18.2 ? #1040
Comments
Yanked. We'll have to add ipywidgets to our downstream tests before attempting another release. |
I agree
On Tue, 29 Nov 2022 at 17:49, Steven Silvester ***@***.***> wrote:
Yanked. We'll have to add ipywidgets to our downstream tests before
attempting another release.
—
Reply to this email directly, view it on GitHub
<#1040 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANPEPISZL7JJP7R3U3JRADWKYXYFANCNFSM6AAAAAASOWA3J4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Maarten Breddels
Software engineer / consultant / data scientist
Python / C++ / Javascript / Jupyter
www.maartenbreddels.com / vaex.io
***@***.*** +31 6 2464 0838 <+31+6+24640838>
[image: Twitter] <https://twitter.com/maartenbreddels>[image: Github]
<https://github.com/maartenbreddels>[image: LinkedIn]
<https://linkedin.com/in/maartenbreddels>[image: Skype]
|
For the record, for |
correct |
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Steven Silvester <steven.silvester@ieee.org> Fixes #1040
When I try using ipykernel 6.18.3 with current ipywidgets in jupyterlab, I get a lot of "No such comm: ..." messages whenever I try to manipulate a widget (sounds like the same thing as @pllim was mentioning above). Was ipykernel 6.18.3 supposed to fix these messages? |
Ah, I see now that 6.18.3 was yanked on pypi. I was still seeing errors installing from conda-forge, since 6.18.1 and 6.18.2 are still up there. conda-forge/admin-requests#520 marks these as broken. |
We added ipywidgets as a downstream test in #1042, but the test suite apparently does not capture dynamic widget messages. In #1043 (comment) I recommended that we back out these changes to comm altogether. Another path is to add testing in ipywidgets that would have covered this case, and make sure those tests pass before attempting another ipykernel release. |
Seems like this release also breaks stuff, ipywidget CI doesn't run:
jdaviz (ipywidget based) is completely broken:
I'm looking into it, but better to avoid many unhappy users.
The text was updated successfully, but these errors were encountered: