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.18:38:58
SpamBayes Score 5.76995e-06
Marked as misclassified No
Message-id <1313692608.3602.29.camel@localhost.localdomain>
In-reply-to <4E4D5B2A.4040700@v.loewis.de>
Content
> > Really, it's not difficult to understand that code testing for "linux2"
> > will stop working when "linux3" gets released.
> 
> This doesn't matter. People will still complain. And, as there is an
> obvious work-around, why not make people's lives easier?

At the cost of some additional confusion, though.
History
Date User Action Args
2011-08-18 18:38:59pitrousetrecipients: + 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 18:38:58pitroulinkissue12326 messages
2011-08-18 18:38:58pitroucreate