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 neologix
Recipients Arfrever, Ramchandra Apte, amaury.forgeotdarc, barry, djc, dmalcolm, 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-18.13:15:55
SpamBayes Score 3.41784e-07
Marked as misclassified No
Message-id <>
In-reply-to <>
> My question too!  I would say that stable releases should probably not get
> this change, but should force sys.platform to linux2 on 3.x kernels.

The point is precisely that we don't change anything: applications
checking against sys.platform are already broken, there's no reason to
comfort them into using this defective check.
The applications that encountered the problem (chromium, matplotlib
and probably others) already performed the change to
sys.platform.startswith(), so it's really the only way to go.

> BTW, does anybody think sys.platform should use a more dynamic approach for
> calculating its value?  Well, maybe not necessary if Python 3.3 will just say
> 'linux'.

There's already platform.system() for that.
Date User Action Args
2011-08-18 13:15:56neologixsetrecipients: + neologix, lemburg, loewis, barry, doko, amaury.forgeotdarc, gagern, foom, pitrou, vstinner, jwilk, djc, ezio.melotti, eric.araujo, Arfrever, r.david.murray, dmalcolm, sandro.tosi, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-18 13:15:55neologixlinkissue12326 messages
2011-08-18 13:15:55neologixcreate