Author barry
Recipients Arfrever, Ramchandra Apte, amaury.forgeotdarc, barry, djc, dmalcolm, doko, ezio.melotti, foom, gagern, haypo, jwilk, lemburg, loewis, merwok, neologix, petri.lehtinen, pitrou, python-dev, r.david.murray, rosslagerwall, sandro.tosi
Date 2011-08-18.15:40:56
SpamBayes Score 4.15157e-08
Marked as misclassified No
Message-id <20110818114050.6a3ee84c@resist.wooz.org>
In-reply-to <CAH_1eM2d4cOEC17P6O9qBmTj4iCPAXjPYONpK0DGUuCbBX=qqg@mail.gmail.com>
Content
On Aug 18, 2011, at 01:15 PM, Charles-François Natali wrote:

>Charles-François Natali <neologix@free.fr> added the comment:
>
>> 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.

I still think that sys.platform for the stable releases should never report
'linux3'.  Updating the various conditionals *probably* has low risk of
regression, but I think you have to check that very carefully.

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

TOOWTDI
History
Date User Action Args
2011-08-18 15:40:57barrysetrecipients: + barry, lemburg, loewis, doko, amaury.forgeotdarc, gagern, foom, pitrou, haypo, jwilk, djc, ezio.melotti, merwok, Arfrever, r.david.murray, dmalcolm, sandro.tosi, neologix, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte
2011-08-18 15:40:56barrylinkissue12326 messages
2011-08-18 15:40:56barrycreate