Steven Silvester

I agree with @Carreau, probably makes sense to add an interrupt call [here](https://github.com/jupyter/jupyter_client/blob/fb919007d3b3dbe02f7516fec4c8ec4cdbeb5a54/jupyter_client/manager.py#L400) using [this logic](https://github.com/jupyter/jupyter_client/blob/fb919007d3b3dbe02f7516fec4c8ec4cdbeb5a54/jupyter_client/manager.py#L437-L441).

Hi @pedroangelini, I think this is related to https://github.com/jupyter/notebook/pull/6221, and should be fixed once that is merged and a new version of `notebook` is released.

Yeah, I think it makes sense for us to track what IPython is doing.

Hi @tungalbert99, I'm not sure why it is hitting the `warnings.warn("Could not import submodules")` condition [here](https://github.com/jupyter/jupyter_client/blob/b2fcb529efc86268fc5e9ead0524bcd2e9585b0c/jupyter_client/__init__.py#L23) in your setup. Can you please try editing `lib/python3.9/site-packages/jupyter_client/__init__.py` to call `raise` after the...

Thanks for the additional context @kendallroth!

@JohanMabille might it be possible to lazily import `from debugpy.server import api` to avoid the side effects at import time?

Hi @adaaaaaa, I think that's because `locust` is using `gevent`, which patches things like `asyncio` and `threading`. This appears to be interfering with the kernel's operation.

Not me personally, no.

If you're referring to `IPython`'s downstream checks, I think the check is using the `pytest` config from `IPython` itself. In the `downstream-test` action in `jupyterlab/maintainer-tools` we made sure to put...

We should be emitting an `error` message in `do_execute` on [error](https://github.com/ipython/ipykernel/blob/10436ea55ce6ad125f2a60644185f293faef3c81/ipykernel/ipkernel.py#L402), the same way we do in [`do_apply`](https://github.com/ipython/ipykernel/blob/10436ea55ce6ad125f2a60644185f293faef3c81/ipykernel/ipkernel.py#L629).