This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ralf.gommers
Recipients BreamoreBoy, LRN, WhiteTiger, arbitraryvalue, cdavid, cgohlke, cournape, donmez, eric.araujo, giampaolo.rodola, jdpipe, loewis, paul.moore, r.david.murray, ralf.gommers, rpetrov, rubenvb, scott.tsai, simonzack
Date 2015-05-19.20:24:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A few comments from the perspective of what's needed for the scientific Python stack:

1. Of the three options mentioned in msg243605, it's definitely (3) that is of interest. We want to build extensions with MinGW-w64 that work with the standard MSVC Python builds. We've done this with mingw32 for a very long time (which works fine); not being able to do this for 64-bit extensions is the main reason why there are no official 64-bit Windows installers for Numpy, Scipy, etc.

2. There is work ongoing on a mingw-w64 toolchain that would work for the scientific Python stack: It actually works pretty well today, what needs to be sorted out is ensuring long-term maintainability. More details about what it's based on are provided in - I think it's consistent with what Ruben van Boxem recommends. Carl Kleffner, who has done a lot of the heavy lifting on this toolchain, is working with upstream mingw-w64 and with WinPython to ensure not creating yet another incompatible flavor mingw.

3. It's good to realize why making mingw-w64 work is especially important for the scientific Python stack: there's a lot of Fortran code in packages like Scipy, for which there is no free compiler that works with MSVC. So one could use MSVC + ifort + Intel MKL (which is what Enthought Canopy and Continuum Anaconda do), but that's quite expensive and therefore not a good solution for the many of contributors to the core scientific Python stack nor okay from the point of view of needing to provide official binaries that can be redistributed.

Paul's comments on picking a single mingw-w64 version, and that version not being a download from someone's personal homepage, make a lot of sense to me. We (Carl & several core numpy/scipy/scikit-learn devs) happened to have planned a call on this topic soon in order to move towards a long-term sustainable plan. I wouldn't expect everything to be sorted out in a couple of weeks (it's indeed a hard goal), but knowing that Paul is willing to review and merge patches definitely helps.
Date User Action Args
2015-05-19 20:24:39ralf.gommerssetrecipients: + ralf.gommers, loewis, paul.moore, jdpipe, giampaolo.rodola, donmez, scott.tsai, cdavid, eric.araujo, rpetrov, r.david.murray, cgohlke, rubenvb, WhiteTiger, BreamoreBoy, LRN, cournape, arbitraryvalue, simonzack
2015-05-19 20:24:39ralf.gommerssetmessageid: <>
2015-05-19 20:24:39ralf.gommerslinkissue4709 messages
2015-05-19 20:24:39ralf.gommerscreate