Author barry
Recipients Arfrever, Ramchandra Apte, amaury.forgeotdarc, barry, djc, doko, eric.araujo, ezio.melotti, foom, gagern, jwilk, lemburg, loewis, neologix, petri.lehtinen, pitrou, python-dev, r.david.murray, rosslagerwall, sandro.tosi, vstinner
Date 2011-08-16.14:21:04
SpamBayes Score 3.38203e-07
Marked as misclassified No
Message-id <>

>> FTR, for Debian and derivatives, doko chose to use 'linux2' when building on linux3.

>Luckily that has just been reverted.

No, I don't think it has:

On Debian Wheezy and Ubuntu 11.10:

$ python2.7 -c 'import sys; print sys.platform'
$ python3.2 -c 'import sys; print(sys.platform)'

oneiric$ uname -a
Linux resist 3.0.0-8-generic #11-Ubuntu SMP Fri Aug 12 20:23:58 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
wheezy$ uname -a
Linux chemistry 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux

I agree with MvL that Python 3.3 should set sys.platform to 'linux' and all stable releases should be patched to return 'linux2' on MACHDEP='linux3' systems. already special cases cygwin* and darwin* to the major-version-number-less platform string, so this doesn't seem like much of a stretch to me for linux.  Since applications/libraries that already test against literal sys.platform values will be broken no matter what we do (except perhaps retain 'linux2' for perpetuity, which doesn't seem like a good idea), I think we should make a clean break from the major version number in Python 3.3 and keep backward compatibility for released Pythons.  Seems like the least worst option to me.
Date User Action Args
2011-08-16 14:21:06barrysetrecipients: + barry, lemburg, loewis, doko, amaury.forgeotdarc, gagern, foom, pitrou, vstinner, jwilk, djc, ezio.melotti, eric.araujo, Arfrever, r.david.murray, sandro.tosi, neologix, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-16 14:21:05barrysetmessageid: <>
2011-08-16 14:21:05barrylinkissue12326 messages
2011-08-16 14:21:04barrycreate