[Python-Dev] Moving Python 3.5 on Windows to a new compiler (original) (raw)
Nathaniel Smith njs at pobox.com
Sat Jun 7 00:47:49 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 Fri, Jun 6, 2014 at 11:43 PM, Sturla Molden <sturla.molden at gmail.com> wrote:
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.
This would require recompiling all packages on OS X and Linux, even though nothing had changed.
-- Nathaniel J. Smith Postdoctoral researcher - Informatics - University of Edinburgh http://vorpus.org
- 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 ]