[Python-Dev] Moving Python 3.5 on Windows to a new compiler
Chris Angelico
rosuav at gmail.com
Fri Jun 6 20:19:32 CEST 2014
More information about the Python-Dev mailing list
Fri Jun 6 20:19:32 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 4:12 AM, Steve Dower <Steve.Dower at microsoft.com> wrote: > Chris Angelico wrote: >> On Sat, Jun 7, 2014 at 1:41 AM, Steve Dower <Steve.Dower at microsoft.com> wrote: >>> What this means for Python is that C extensions for Python 3.5 and later can be built using any version of MSVC from 14.0 and later. >> >> Oh, if only this had been available for 2.7!! Actually... this means that 14.0 would be a good target for a compiler change for 2.7.x, if such a change is ever acceptable. > > Maybe, but I doubt it will ever be acceptable :) Well, there were discussions. Since Python 2.7's support is far exceeding the Microsoft promise of support for the compiler it was built on, there's going to be a problem, one way or the other. I don't know how that's going to end up being resolved. 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