Home Original page

[Python-Dev] Moving Python 3.5 on Windows to a new compiler

Terry Reedy tjreedy at udel.edu
Sat Jun 7 03:05:53 CEST 2014 
On 6/6/2014 6:47 PM, Nathaniel Smith wrote:
> 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.

If you are suggesting that a Windows compiler change should be invisible 
to non-Windows users, I agree.

Let us assume that /pcbuild remains for those who have vc2008 and that 
/pcbuild14 is added (and everything else remains as is). Then the only 
other thing that would change is the Windows installer released on 
Python.org. Call than 2.7.9W or whatever on the download site and 
interactive startup message to signal that something is different.

-- 
Terry Jan Reedy
More information about the Python-Dev mailing list