Message142382
| Author | loewis |
|---|---|
| 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.17:48:02 |
| SpamBayes Score | 0.00013904815 |
| Marked as misclassified | No |
| Message-id | <4E4D5051.1050407@v.loewis.de> |
| In-reply-to | <1313683902.3602.13.camel@localhost.localdomain> |
| Content | |
|---|---|
> It means someone upgrading from 2.6 to 2.7 will see sys.platform change > from "linux3" to "linux2". That breaks compatibility. No, it doesn't. Code that works on 2.6 and Linux 3 will likely support both linux2 and linux3, so it will continue just fine on 2.7. I'd rather phrase this differently: Python 2.6 does not support Linux 3. Tough luck, since Linux 3 was released long after Python 2.6. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-08-18 17:48:03 | loewis | set | recipients: + loewis, lemburg, 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 17:48:03 | loewis | link | issue12326 messages |
| 2011-08-18 17:48:02 | loewis | create | |