kevin-bates
commented
2 years ago This seems reasonable. I suppose we'll need to wait until support for 3.7 expires since importlib.metadata is new in 3.8, or build an abstraction layer that's sensitive to the python version.
Can you please share more about the context and nature of the conflict in which this issue occurred for you? This might help us better determine the issue's priority. (Thank you)
Ran into an issue building a Docker image that involved jupyter-client, and a conflicting entrypoints version. The work around was to hard pin entrypoints in our code. But as that project is in maintenance mode, it might be nice to decouple jupyter-client from it.