Skip to content

Support __version__ #175

Dec 15, 2020 · 2 comments · 1 reply
Discussion options

You must be logged in to vote

IMO: We should! In my packages, it's kind of hit-or-miss, often based on some bad practices that have become hard to change. :/ But in general top_level_module.__version__ is the right place for a version number.

Side question: What's the accepted practice for comparing string-y version numbers? I know distutils/setuptools has something... is that what you're supposed to use? (That's why I have VERSION in my packages as a tuple-y version number, so that VERSION >= (2020, 4) does something vaguely sensible.)

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@matthiasdiener
Comment options

Answer selected by matthiasdiener
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants