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 loewis
Recipients Arfrever, amaury.forgeotdarc, lemburg, loewis, neologix, pitrou, rosslagerwall, vstinner
Date 2011-06-14.06:11:19
SpamBayes Score 7.9184437e-10
Marked as misclassified No
Message-id <4DF6FB86.4070500@v.loewis.de>
In-reply-to <1308030473.25.0.530238569697.issue12326@psf.upfronthosting.co.za>
Content
> This change is reasonable for the long term.  But it *will* break a lot of code.

[If you favor a specific change, please indicate what that is. I'm
assuming you support my proposal for the moment :-]

I agree it will break a lot of code, but it's also somewhat urgent
because we will get 'linux3' if we don't act, which will also break
a lot of code (but more subtly, since people testing their code may
do so on Linux 2, only to get bug reports that it breaks on "some"
Linux systems). I'm sure Linus Torvalds is fully aware of the possible
consequences of the version change, and just accepted the breakage
that this would cause.

It's important that we set a policy before the Linux distributions
do (which may end up choosing different policies). We don't actually
have to *release* this change quickly, since Linux distributions
who release 3.x kernels will fix their Python packages themselves.
History
Date User Action Args
2011-06-14 06:11:20loewissetrecipients: + loewis, lemburg, amaury.forgeotdarc, pitrou, vstinner, Arfrever, neologix, rosslagerwall
2011-06-14 06:11:19loewislinkissue12326 messages
2011-06-14 06:11:19loewiscreate