David Brochart

> @davidbrochart thank you! It works. :tada: > Anyway, the kernel connection info is not created automatically. I write it manually. Is it a bug? Could be, it would be...

1. You need to ask your kernel manager to [shutdown the kernel](https://github.com/jupyter/jupyter_client/blob/692bc307270fb98b48dddf024a7e533a578495eb/jupyter_client/manager.py#L466), otherwise the kernel continues living even after `process1.py` has exited. You can get the [running kernels](https://github.com/jupyter/jupyter_client/blob/692bc307270fb98b48dddf024a7e533a578495eb/jupyter_client/multikernelmanager.py#L131-L139) from a...

> somehow the `KernelManager` is not connected, it returns `False` for `is_alive()` method. It is currently considered alive if it [launched the kernel](https://github.com/jupyter/jupyter_client/blob/830453faaf7e4005c4104b9b47e856d4949d1791/jupyter_client/provisioning/local_provisioner.py#L204).

Thanks @RRosio, could you point to the failing tests (I assume it's reproducible in a CI)?

Yes but not released yet.

You should see something like this: 

It's `plt.scatter`, not `plt.plot`.

Thanks for bringing that up @RobertRosca! You're right, Jupyter is moving to using Hatch in general, and the features you've listed would be very beneficial to Jupyverse. As you seem...

Awesome, and no worries!

@RobertRosca I switched to hatch in #227. It should be equivalent to what we had before with setuptools, but there is none of the potential improvements your described in this...