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 paul.moore
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.22:17:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ralf, thanks for the comments. The scientific community is definitely the key group that *need* mingw (as opposed to people who merely want to use it because they don't want to buy into MS compilers, or for similar personal reasons).

My personal view is that if the scientific community comes up with a mingw/gcc toolchain that they are happy with, and willing to support, then I would see that as a reasonable target to be "the" supported mingw toolchain for distutils.

I'd like to see a single-file "download, unzip, and use" distribution rather than the current rather intimidating set of instructions on how to set the toolchain up - but I'm sure that's part of what you're intending to cover under "ensuring long-term maintainability".
Date User Action Args
2015-05-19 22:17:59paul.mooresetrecipients: + paul.moore, loewis, jdpipe, giampaolo.rodola, donmez, scott.tsai, cdavid, eric.araujo, rpetrov, r.david.murray, cgohlke, rubenvb, WhiteTiger, BreamoreBoy, LRN, cournape, arbitraryvalue, ralf.gommers, simonzack
2015-05-19 22:17:59paul.mooresetmessageid: <>
2015-05-19 22:17:59paul.moorelinkissue4709 messages
2015-05-19 22:17:59paul.moorecreate