Repository navigation
Querying installed version using importlib.metadata - #3532
Merged
leowerneck merged 1 commit intoOct 2, 2026
Merged
Conversation
leowerneck
approved these changes
Oct 2, 2026
leowerneck
merged commit Oct 2, 2026
4b14732
into
IMAP-Science-Operations-Center:dev
22 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #3531.
The backend
poetry_dynamic_versioning.backendis doing the right thing and generating the correct version in the METADATA file. So the entire dance with the_version.pycan simply be removed, and theimportlib.metadatamodule used to query this version at runtime.A test has been added to ensure the correct version (non-zero) is reported after installation.
I've tested the logs produced by
imap_cli's processing and they're spitting out the correct version as well.