You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2023. It is now read-only.
For our package management we use automated tooling to extract version numbers from python packages. I would like to request that you add the __version__ attribute version string.
On a case-by-case basis, standard library modules which are also released in standalone form for other Python versions MAY include a module version number when included in the standard library, and SHOULD include a version number when packaged separately.
When a module (or package) includes a version number, the version SHOULD be available in the __version__ attribute.
The __version__ attribute's value SHOULD be a string.
The text was updated successfully, but these errors were encountered:
ddriddle
added a commit
to ddriddle/traceback2
that referenced
this issue
May 6, 2015
Thank you for the report and for the PR. Note that PEP 396 is not an accepted PEP and we recently got rid of several __version__ attributes in both standard library and their backports (see email for example) Also, some of the recent standard library modules and their backports don't even have __version__ attributes. See selectors34 for example.
And usually importing the module itself in setup.py is a bad practice.
For our package management we use automated tooling to extract version numbers from python packages. I would like to request that you add the
__version__
attribute version string.PEP 396 states:
__version__
attribute.__version__
attribute's value SHOULD be a string.The text was updated successfully, but these errors were encountered: