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 steve.dower
Recipients Bruno Abreu Calfa, dstufft, eric.araujo, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-01-12.02:09:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515722949.2.0.467229070634.issue32535@psf.upfronthosting.co.za>
In-reply-to
Content
The CRT isn't a simple DLL anymore, and MinGW isn't a fully supported compiler either. You're going to be best to work with the people behind mingwpy to get it working, as there really isn't anything we can do on our end (though I do what I can to help them out, short of committing code).

As I understand it, work on mingwpy has basically stopped right now for a variety of reasons, and most projects have found ways to work with MSVC. 

I'm going to close this bug as external. When there is something for us to change in core, then we can consider it. (About the only thing worth doing right now is fully removing the mingw support to avoid confusion, but there's no value in that so why bother.)
History
Date User Action Args
2018-01-12 02:09:09steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, eric.araujo, zach.ware, dstufft, Bruno Abreu Calfa
2018-01-12 02:09:09steve.dowersetmessageid: <1515722949.2.0.467229070634.issue32535@psf.upfronthosting.co.za>
2018-01-12 02:09:09steve.dowerlinkissue32535 messages
2018-01-12 02:09:07steve.dowercreate