[Python-Dev] Moving Python 3.5 on Windows to a new compiler
Sturla Molden
sturla.molden at gmail.com
Sat Jun 7 00:43:34 CEST 2014
More information about the Python-Dev mailing list
Sat Jun 7 00:43:34 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 ]
Brett Cannon <bcannon at gmail.com> wrote: > Nope. A new minor release of Python is a massive undertaking which is why > we have saved ourselves the hassle of doing a Python 2.8 or not giving a > clear signal as to when Python 2.x will end as a language. Why not just define Python 2.8 as Python 2.7 except with a newer compiler? I cannot see why that would be massive undertaking, if changing compiler for 2.7 is neccesary anyway. Sturla
- 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