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 fratti
Recipients Jeffrey.Armstrong, Martin.Fiers, Pete.Forman, RubyTuesdayDONO, Seppo.Yli-Olli, alexis, cmcqueen1975, danmbox, doko, eric.araujo, fratti, geertj, jonforums, jwilk, loewis, oscarbenjamin, paul.moore, pje, renatosilva, rpetrov, rubenvb, santoso.wijaya, schmir, tarek
Date 2013-06-23.18:09:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It's cool that you guys are discussing semantics of who said what and how, but that still doesn't fix this very simple issue that breaks compiling for everyone on Windows who uses MinGW.
-mno-cygwin, was, as far as I know, only ever required to build from cygwin as host to mingw as target.
It is very unlikely that anyone who'd upgrade python still needs this option and is running a gcc cygwin 3.x version. And if it breaks for them it's still better than the current state, which is "broken for everyone else".

Sorry if this sounds snarky, but the fact that this issue has been open for almost 2 years is quite ridiculous.
Date User Action Args
2013-06-23 18:09:48frattisetrecipients: + fratti, loewis, doko, paul.moore, pje, geertj, schmir, tarek, jwilk, eric.araujo, rpetrov, cmcqueen1975, rubenvb, santoso.wijaya, alexis, Seppo.Yli-Olli, jonforums, RubyTuesdayDONO, Jeffrey.Armstrong, danmbox, Martin.Fiers, oscarbenjamin, Pete.Forman, renatosilva
2013-06-23 18:09:48frattisetmessageid: <>
2013-06-23 18:09:48frattilinkissue12641 messages
2013-06-23 18:09:48fratticreate