-
-
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
Release 7.0 #1222
Comments
cc @ianthomas23 |
Perhaps this is the reason why Qtconsole tests are failing because it supports an in-process frontend.
We have an upper constraint on IPykernel ( |
Good to know, thanks. If not, we can pin Qtconsole to ( For |
I started looking at the jupyter-client tests, test_start_sequence_kernels at least will be fixed by agronholm/anyio#714. |
I'm stepping down from maintenance, so I won't be able to complete this release. |
Listing some of the changes:
|
Would it be OK to drop Python 3.8 for this release? It reached end-of-life on 2024-10-07. |
Yes I think so. |
For what it is worth, IPython follows spec-0000 so IPython is going to drop 3.10 soon. |
main
is currently targetingipykernel
7.0, with support for AnyIO.We have to address the following before releasing:
inprocess
tests are failing after Replace Tornado with AnyIO #1079, and are currently skippedjupyter_client
tests are failing. We will need to make a release that supports bothipykernel
6.0 and 7.0qtconsole
tests are failing. We will need to make a release that supports bothipykernel
6.0 and 7.0, or a release that pins to (<7.0
).<7.0
) in metakernel for now - Add compatibility with IPyKernel 7.0 Calysto/metakernel#275The text was updated successfully, but these errors were encountered: