[Python-Dev] Moving Python 3.5 on Windows to a new compiler
Chris Angelico
rosuav at gmail.com
Fri Jun 6 21:33:45 CEST 2014
More information about the Python-Dev mailing list
Fri Jun 6 21:33:45 CEST 2014
- Previous message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Next message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Jun 7, 2014 at 5:11 AM, Donald Stufft <donald at stufft.io> wrote: > Is it really any difference in maintenance if you just stop applying updates to > 2.7 and switch to 2.8? If 2.8 is really just 2.7 with a new compiler then there > should be no functional difference between doing that and doing a 2.7.whatever > except all of the tooling that relies on the compiler not to change in micro > releases won’t suddenly break and freak out. If the only difference between 2.7 and 2.8 is the compiler used on Windows, what happens on Linux and other platforms? A Python 2.8 would have to be materially different from Python 2.7, not just binarily incompatible on one platform. ChrisA
- Previous message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Next message: [Python-Dev] Moving Python 3.5 on Windows to a new compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list