Release 7.0

[blink1073]

main is currently targeting ipykernel 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 skipped
• jupyter_client tests are failing. We will need to make a release that supports both ipykernel 6.0 and 7.0
• qtconsoletests are failing. We will need to make a release that supports both ipykernel 6.0 and 7.0, or a release that pins to (<7.0).
• Minimum Version tests are failing. We will need to update minimum versions to get that passing.
• Pin to (<7.0) in metakernel for now - Add compatibility with IPyKernel 7.0 Calysto/metakernel#275
• Add migration documentation (it might be helpful to write this while updating Metakernel)

[blink1073]

cc @davidbrochart @ccordoba12

[blink1073]

cc @ianthomas23

[ccordoba12]

inprocess tests are failing after #1079, and are currently skipped

Perhaps this is the reason why Qtconsole tests are failing because it supports an in-process frontend.

spyder_kernels tests are failing. We will need to make a release that supports both ipykernel 6.0 and 7.0

We have an upper constraint on IPykernel (< 7.0), so we'll only need to add support for ipykernel 7.0 in a minor Spyder-kernels release.

[blink1073]

Perhaps this is the reason why Qtconsole tests are failing because it supports an in-process frontend.

Good to know, thanks. If not, we can pin Qtconsole to (<7.0) as well.

For jupyter_client, I think it is a matter of updating the tests only, which use classes from ipykernel.

[davidbrochart]

I started looking at the jupyter-client tests, test_start_sequence_kernels at least will be fixed by agronholm/anyio#714.