Message142409
| Author | lemburg |
|---|---|
| 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.23:17:23 |
| SpamBayes Score | 5.0610636e-09 |
| Marked as misclassified | No |
| Message-id | <4E4D9D7C.8070701@egenix.com> |
| In-reply-to | <20110818185544.1950b20f@resist.wooz.org> |
| Content | |
|---|---|
Barry A. Warsaw wrote: > > Barry A. Warsaw <barry@python.org> added the comment: > > On Aug 18, 2011, at 05:54 PM, Martin v. Löwis wrote: > >> As for the cases where "linux3" is reported: I don't care that >> they break. Python 2.6 and Python 2.7.2 is incompatible with >> Linux 3. Users should be advised to a) not upgrade to Linux 3, or >> b) simultaneously upgrade to a newer Python release, or >> c) work-around in their applications. >> >> I expect that most users chose a) for some time to come (until >> the Linux distributions ship the new kernels), and that the Linux >> distributions chose b) and c). > > In fact, for Debian and Ubuntu, we had several breakages due to sys.platform > == 'linux3' so for all Pythons we still support, we're going to force it back > to 'linux2'. This fixed all those broken packages without any of them needing > to be changed. Ah, those lazy Debian/Ubuntu folks again ;-) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-08-18 23:17:24 | lemburg | set | recipients: + lemburg, loewis, barry, doko, amaury.forgeotdarc, gagern, foom, pitrou, vstinner, jwilk, djc, ezio.melotti, eric.araujo, Arfrever, r.david.murray, dmalcolm, sandro.tosi, rosslagerwall, python-dev, petri.lehtinen, Ramchandra Apte |
| 2011-08-18 23:17:24 | lemburg | link | issue12326 messages |
| 2011-08-18 23:17:23 | lemburg | create | |