Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Regression with setuptools 27.2.0 on appveyor with Windows + Python 3.5 + numpy 1.11.1 #790
We have a regression on Windows + Python 3.5 + numpy 1.11.1 on our project when compiling with appveyor.
The issue is relative to unquoted path at linking step:
I try to reproduce the problem with an own Windows machine without success. Then i only have the issue on appveyor + Python 3.5 + numpy 1.11.1
Here is few tests executed on appveyor according to setuptools versions
While i can't reproduce the problem on an own computer it is very difficult to know what's append. But do you have an idea?
BTW, there is a very mysterious message:
So I think you're reporting a regression with 27.1.0 from 27.0.0, and here are the differences. Basically, the monkeypatching logic was consolidated in a new monkey module. There were known defects (specifically addressing the patching of MSVC) with v27.1.0 which were fixed in v27.1.1 and v27.1.2. Can you test v27.1.2?
Then i guess the problem come from
But i guess, if
Then maybe there is no other choices than something like that to really patch
I appreciate you working out a technique that works. That's helpful. I'd like to work out what it is about your implementation that fixes the numpy build. I'd like to either have a test in setuptools that captures the expectation that numpy has about the monkeypatching or somehow add an integration test that will capture the actual numpy expectation.
Based on your investigation, can you imagine a unit test that would capture the expectation that your changes meet?
Sorry, i was very busy this days.
The problem is that part of
Right now the setuptools code is nice, but using
I guess the problem is somewhere here. There is no way to use
Anyway, i dont really know why the behaviour on my Windows computer and on appveyor is not the same. I dont really reach deeply on that, cause it is laborious.