Barry A. Warsaw added the comment: 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.
---------- resolution: -> wont fix status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19889> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
