Mon Oct 11 13:39:31 CDT 2010
The behaviour is there in regular distutils, it is apparently a known
bug, I'm copy/pasting their answer in there for information.
Answer (from Tarek Ziade):
This is a regression I introduced to fix the fact that the .so are not
rebuilt we you do subtle changes in your project.
We ended up reverting this, and the changes will be done in
Distutils2. see: http://BLOCKEDbugs.python.org/issue8688 for the details.
On 10/7/10 9:39 PM, David Cournapeau wrote:
> On Fri, Oct 8, 2010 at 7:40 AM, Charles Doutriaux <firstname.lastname@example.org> wrote:
>> Did anybody else noticed this? Anybody know what changed (the fact that
>> it's since Python 2.7 make me think it might be pure distutils related)
> Could you check whether you still see the issue without using
> numpy.distutils ? I actually would be surprised to see it as a
> distutils issue proper, as somebody would have almost certainly
> noticed it already.
>> Any insight on how distuils and numpy.distutils are related would be
>> great too!
> numpy.distutils uses distutils, but in an unconvential way, because it
> needs to hook itself to internals. Hence, any non trivial change (and
> even trivial, sometimes) can break numpy.distutils.
> NumPy-Discussion mailing list
More information about the NumPy-Discussion