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 eric.araujo
Recipients alexis, eric.araujo, jonforums, rubenvb, schmir, tarek
Date 2011-07-27.15:07:45
SpamBayes Score 2.0769325e-10
Marked as misclassified No
Message-id <>
I forgot to answer this:

> Why is -mno-cygwin still be used,
Simply because distutils had no dedicated maintainer for a long time, and because nobody was aware of this change.  I don’t think any Python core developer is using Cygwin.

> and is there any reason why it can't be removed?
For distutils, we have to work on eggshells when fixing bugs to make sure we don’t break third-party code that relies on known bugs or works around them.  That’s why I propose adding a version check* instead of just removing the option.

* i.e. removing -mno-cygwin if self.gcc_version >= some version
Date User Action Args
2011-07-27 15:07:45eric.araujosetrecipients: + eric.araujo, schmir, tarek, rubenvb, alexis, jonforums
2011-07-27 15:07:45eric.araujosetmessageid: <>
2011-07-27 15:07:45eric.araujolinkissue12641 messages
2011-07-27 15:07:45eric.araujocreate