Message141231
| 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 |
<1311779265.94.0.706961030331.issue12641@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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 |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年07月27日 15:07:45 | eric.araujo | set | recipients:
+ eric.araujo, schmir, tarek, rubenvb, alexis, jonforums |
| 2011年07月27日 15:07:45 | eric.araujo | set | messageid: <1311779265.94.0.706961030331.issue12641@psf.upfronthosting.co.za> |
| 2011年07月27日 15:07:45 | eric.araujo | link | issue12641 messages |
| 2011年07月27日 15:07:45 | eric.araujo | create |
|