[issue46774] Importlib.metadata.version picks first distribution not latest

Jason R. Coombs added the comment: Closing without prejudice. Happy to revisit if there's more information on how importlib could/should behave differently. -- stage: -> resolved status: open -> closed ___ Python tracker

[issue46774] Importlib.metadata.version picks first distribution not latest

Jason R. Coombs added the comment: Aha. I learned how to run commands in the poetry environment... and how to locate files in that environment. With that, I figured out where the environment is and where the package metadata is coming from: ``` $ docker run -it @$(docker build -q .) bash -c

[issue46774] Importlib.metadata.version picks first distribution not latest

Jason R. Coombs added the comment: The behavior you describe is intentional _and_ deterministic. The library discovers distributions in the order found based on the search path provided, with the search path defaulting to sys.path. The expectation is therefore that the metadata should be

[issue46774] Importlib.metadata.version picks first distribution not latest

Change by Alex Waygood : -- nosy: +jaraco ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46774] Importlib.metadata.version picks first distribution not latest

Change by Kevin Kirsche : -- nosy: +kkirsche ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46774] Importlib.metadata.version picks first distribution not latest

New submission from Kevin Kirsche : When using importlib.metadata.version with tools such as poetry which may install the current package one or more times, importlib.metadata.version is not deterministic in returning the latest version of the package, instead returning the first one