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 loewis
Recipients eric.araujo, georg.brandl, loewis, t-kamiya, terry.reedy
Date 2010-07-31.19:53:18
SpamBayes Score 3.785534e-06
Marked as misclassified No
Message-id <1280606000.54.0.588711873853.issue5778@psf.upfronthosting.co.za>
In-reply-to
Content
On OS X, it's still something like

2.6.5 (r265:79359, Mar 24 2010, 01:32:55) 
[GCC 4.0.1 (Apple Inc. build 5493)]

on Redhat, it once was

2.3.4 (#1, Oct 26 2004, 16:42:40) 
[GCC 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)]

Apple once had

2.3 (#1, Sep 13 2003, 00:49:11) 
[GCC 3.3 20030304 (Apple Computer, Inc. build 1495)]

I also found

2.2.2 (#0, Mar 23 2007, 12:02:04)
[GCC 2.9-psion-98r2 (Symbian build 546)]

2.4.4 (#2, Apr  5 2007, 20:11:18)
[GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)]

Python 2.2.2 (#1, Oct 28 2002, 17:22:19)
[GCC 3.2 (Mandrake Linux 9.0 3.2-1mdk)]

I recommend to close this as "won't fix". There is no promise that sys.version follows any particular syntax. Developers should use sys.version_info instead, and the platform module (e.g. platform.python_compiler())
History
Date User Action Args
2010-07-31 19:53:20loewissetrecipients: + loewis, georg.brandl, terry.reedy, eric.araujo, t-kamiya
2010-07-31 19:53:20loewissetmessageid: <1280606000.54.0.588711873853.issue5778@psf.upfronthosting.co.za>
2010-07-31 19:53:19loewislinkissue5778 messages
2010-07-31 19:53:18loewiscreate