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 pitrou
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.17:58:26
SpamBayes Score 8.51884e-06
Marked as misclassified No
Message-id <1313690175.3602.17.camel@localhost.localdomain>
In-reply-to <4E4D5051.1050407@v.loewis.de>
Content
> > It means someone upgrading from 2.6 to 2.7 will see sys.platform change
> > from "linux3" to "linux2". That breaks compatibility.
> 
> No, it doesn't. Code that works on 2.6 and Linux 3 will likely support
> both linux2 and linux3, so it will continue just fine on 2.7.

Then, let's just advise that all code follow the same path and use
sys.platform.startswith() (which is really not a difficult change to
make).
History
Date User Action Args
2011-08-18 17:58:26pitrousetrecipients: + pitrou, lemburg, loewis, barry, doko, amaury.forgeotdarc, gagern, foom, vstinner, jwilk, djc, ezio.melotti, eric.araujo, Arfrever, r.david.murray, dmalcolm, sandro.tosi, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-18 17:58:26pitroulinkissue12326 messages
2011-08-18 17:58:26pitroucreate