Hi @AOrazaev, we should definitely change the error message specifically for local-provisioner since that provisioner is directly baked into jupyter_client (7.0+) as its confusing relative to that provisioner. As noted in the linked thread, it should be present so there’s some way that the jupyter_client code is made available w/o the requisite entrypoint registration - which is how local-provisioner is deemed available.
Do you or others happen to know by which “installation or packaging” mechanism entrypoints get registered? There’s obviously some path in which the package modules are made available, yet package-specific entrypoints are not.
Thank you.