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 foom
Recipients Arfrever, Ramchandra Apte, amaury.forgeotdarc, 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-05.14:05:14
SpamBayes Score 1.0238e-07
Marked as misclassified No
Message-id <>
Oh wow, so it depends on the *build* time major version? That's really not useful at all for linux 2.x and 3.x; there is nothing useful anyone can possibly do with the distinction between platform == "linux2" and platform == "linux3". All it could possibly do is to break apps.

Given that:
a) old versions of Python won't even build without a patch and
b) changing platform to linux3 will break a lot of python apps that check sys.platform. 
c) It's completely useless to change it, as the change contains no actual information.

Why is forcing sys.platform to remain linux2 not the *obviously right thing to do*?
Date User Action Args
2011-08-05 14:05:14foomsetrecipients: + foom, lemburg, loewis, doko, amaury.forgeotdarc, gagern, pitrou, vstinner, jwilk, djc, ezio.melotti, eric.araujo, Arfrever, r.david.murray, sandro.tosi, neologix, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-05 14:05:14foomsetmessageid: <>
2011-08-05 14:05:14foomlinkissue12326 messages
2011-08-05 14:05:14foomcreate