➜
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.
Created on 2013-12-04 22:24 by lemburg, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg205256 - (view) | Author: Marc-Andre Lemburg (lemburg) *  |
Date: 2013-12-04 22:24 | |
Not sure whether this can be considered a bug, but Python 2.6.7 for example showed the build revision in the sys.version: >>> sys.version '2.6.7 (r267:88850, Feb 9 2012, 18:56:05) \n[GCC 4.5.0 20100604 [gcc-4_5-branch revision 160292]]' whereas Python 2.6.9 does not: >>> sys.version '2.6.9 (unknown, Dec 4 2013, 18:39:21) \n[GCC 4.5.0 20100604 [gcc-4_5-branch revision 160292]]' |
|||
| msg205264 - (view) | Author: Barry A. Warsaw (barry) * |
Date: 2013-12-05 00:17 | |
I think this is due to the switch from Subversion to Mercurial, which if I'm reading PEP 385 and remembering correctly, happened about the time of Python 2.6.7. IIRC, we released that source tarball from Subversion so you're seeing svn build number. When we switched to Mercurial, it was decided not to fix sys.version to understand hg version numbers, since we were in source-only security-only mode. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:55 | admin | set | github: 64088 |
| 2013-12-05 00:17:13 | barry | set | status: open -> closed resolution: wont fix messages: + msg205264 |
| 2013-12-04 22:35:34 | ned.deily | set | nosy:
+ barry |
| 2013-12-04 22:24:04 | lemburg | create | |