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 vstinner
Recipients Arfrever, Ramchandra Apte, amaury.forgeotdarc, barry, djc, dmalcolm, doko, eric.araujo, ezio.melotti, foom, gagern, jwilk, lemburg, loewis, petri.lehtinen, pitrou, python-dev, r.david.murray, rosslagerwall, sandro.tosi, vstinner
Date 2011-08-18.16:26:50
SpamBayes Score 2.83591e-06
Marked as misclassified No
Message-id <1313684811.69.0.750186706718.issue12326@psf.upfronthosting.co.za>
In-reply-to
Content
If we change Python 2.7.3 and 3.2.2 to force sys.platform to linux2 (instead of linux3) and use "linux" in Python 3.3, we will have 3 differents values of sys.platform if Python is built on Linux 3:

 - "linux3" on Python <= 2.7.2 or Python <= 3.2.1
 - "linux2" on 2.7.3 <= Python or 3.2.2 <= Python < 3.3
 - "linux" on Python >= 3.3

I don't see how it will help backward or forward compatibility... It's exactly as the current state (sys.platform == 'linux3' on all Python versions): applications have to use sys.platform.startswith() to work correctly on any Linux version.

Well, except maybe if you plan to write applications working only on Python >= 2.7.3? ... this version is not released yet.
History
Date User Action Args
2011-08-18 16:26:51vstinnersetrecipients: + vstinner, lemburg, loewis, barry, doko, amaury.forgeotdarc, gagern, foom, pitrou, jwilk, djc, ezio.melotti, eric.araujo, Arfrever, r.david.murray, dmalcolm, sandro.tosi, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-18 16:26:51vstinnersetmessageid: <1313684811.69.0.750186706718.issue12326@psf.upfronthosting.co.za>
2011-08-18 16:26:51vstinnerlinkissue12326 messages
2011-08-18 16:26:50vstinnercreate