Author loewis
Recipients Arfrever, Ramchandra Apte, amaury.forgeotdarc, barry, djc, dmalcolm, doko, ezio.melotti, foom, gagern, haypo, jwilk, lemburg, loewis, merwok, petri.lehtinen, pitrou, python-dev, r.david.murray, rosslagerwall, sandro.tosi
Date 2011-08-18.17:43:33
SpamBayes Score 4.02273e-06
Marked as misclassified No
Message-id <4E4D4F44.9060502@v.loewis.de>
In-reply-to <CAH_1eM2d4cOEC17P6O9qBmTj4iCPAXjPYONpK0DGUuCbBX=qqg@mail.gmail.com>
Content
> 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.

You grossly misunderstand the concept of "backwards compatibility".
At times, features get added to allow even buggy (or perceived-buggy)
applications to continue to work under a change.

> 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.

I'm very certain that not all applications have been changed yet.
History
Date User Action Args
2011-08-18 17:43:34loewissetrecipients: + loewis, lemburg, barry, doko, amaury.forgeotdarc, gagern, foom, pitrou, haypo, jwilk, djc, ezio.melotti, merwok, Arfrever, r.david.murray, dmalcolm, sandro.tosi, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-18 17:43:33loewislinkissue12326 messages
2011-08-18 17:43:33loewiscreate