This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author takluyver
Recipients takluyver
Date 2015-08-22.17:52:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440265954.47.0.288307978254.issue24916@psf.upfronthosting.co.za>
In-reply-to
Content
sysconfig currently calculates various formats of the Python version number by chopping up the sys.version string. This has a FIXME by it in the code, because the the format of sys.version is not guaranteed.

With this patch, the config variables 'py_version', 'py_version_short' and 'py_version_nodot' are instead generated from sys.version_info, which has a specified structure:
https://docs.python.org/3/library/sys.html#sys.version_info

One piece of information is lost by this change: after a pre-release, a + is added to the version string - e.g. '3.5.0b4+' means an unreleased version somewhere after 3.5.0b4. I can't find any structured representation of this information, so 'py_version' no longer contains it. I'm not sure whether it matters: I can't find anything using the 'py_version' config variable.
History
Date User Action Args
2015-08-22 17:52:34takluyversetrecipients: + takluyver
2015-08-22 17:52:34takluyversetmessageid: <1440265954.47.0.288307978254.issue24916@psf.upfronthosting.co.za>
2015-08-22 17:52:34takluyverlinkissue24916 messages
2015-08-22 17:52:33takluyvercreate