-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add rich.__version__ #15
Comments
I use poetry to do packaging, which recommends |
Thanks for the feedback. But why is it closed (it's still unimplemented)? Even though poetry is used, we could add this property with a workaround. |
Keeping the version in two places is problematic. But if poetry hasn't got a solution when I release a 1.0 version, that's what I might have to do. In the meantime, the lack of a |
Just a note. For Python 3.8+, importlib.metadata should probably be used instead. And the importlib_metadata backaport exists for other Python 3 versions. It was created to replace pkgresources metadata functionality. Here's how I use it to deduplicate my package metadata. I use poetry, too, and I couldn't wait any longer. I already had that module and was manually updating it. |
I may end up doing something similar... |
Still seems to be missing |
Don't know where you got that idea from. |
I didn't mean to sound adversarial! It was your message above that gave me this impression:
Personally I agree with the OP that it's pretty standard to provide this, but it's up to you of course. |
It was a standard of sorts, but now importlib is recommended, and Unless poetry has an answer to this that doesn't require a backport of importlib, I'm afraid there is no motivation to change it. |
rich
should have__version__
property.This is a common python convention to tell package version easily.
The text was updated successfully, but these errors were encountered: