[Python-Dev] Moving Python 3.5 on Windows to a new compiler (original) (raw)
Sturla Molden sturla.molden at gmail.com
Sat Jun 7 01:01:31 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 ]
Brian Curtin <brian at python.org> wrote:
Adding features into 3.x is already not enough of a carrot on the stick for many users. Intentionally leaving 2.7 on a dead compiler is like beating them with the stick.
Those who want to build extensions on Windows will just use MinGW (currently GCC 2.8.2) instead.
NumPy and SciPy are planning a switch to a GCC based toolchain with static linkage of the MinGW runtime on Windows. It is carefully configured to be binary compatible with VS2008 on Python 2.7. The major reason for this is to use gfortran also on Windows. But the result will be a GCC based toolchain that anyone can use to build extensions on Windows.
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 ]