Use standard __version__ variable for version#1232
Merged
LourensVeen merged 1 commit intoMar 12, 2026
Merged
Conversation
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
1 participant
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.
It turns out hatchling only writes
__version__, so we'll have to make do without the non-standardversion. This updates the literature subsystem to import and use that so that we get correct versions again.I've also removed the catch, which will cause AMUSE to crash if the version isn't found in the future. That should never happen on a correct install (including a development install, because
pip install -ewill create_version.pyalso in that case. If it does happen, then we want to know and fix it, not silently ignore the problem.Fixes #1187.