[Numpy-discussion] numpy 1.3.0 eggs with python2.6 seem broken on osx, and linux
Wed Dec 2 04:53:47 CST 2009
On Sat, Nov 28, 2009 at 2:56 PM, David Cournapeau <firstname.lastname@example.org>wrote:
> On Sat, Nov 28, 2009 at 10:42 PM, René Dudfield <email@example.com> wrote:
> > yeah, I completely understand the unfortunate packaging situation (eg,
> > of my packages do not work with this install method).
> > Here is a simple package requiring numpy. It uses buildout
> > (http://www.buildout.org/). To help easily reproduce the problem, here
> > the commands to reproduce.
> I have not tried it, but from your explanation, I would suspect that
> buildout does some monkeypatching which is not exactly the same as
> setuptools itself, and that would break numpy.distutils.
> The distutils architecture unfortunately requires to take into account
> and special case any distutils extensions, because of the "extension
> as command inheritance" approach. I know I prefer spending my time on
> new packaging solution, but I would take patches.
Package/module semantics changed during 2.6/3.0. I think it might have
something to do with that. Hopefully some of the py3 work will fix these
Actually, I think it might also be a buildout bug. It seems buildout uses
the sys.path variable to add paths to the python interpreter. Whereas the
'proper' way is to use the PYTHONPATH environment imho. Since modifying
sys.path does not affect sub processes paths. It seems numpy uses a sub
process in the install? Or maybe buildout/python2.6 use a subprocess. Or
with 2.5 already having a numpy installed (on osx), then perhaps it was
using the old numpy.distutils already installed to do the install.
Anyway, that's my findings so far. Not sure if I'll look into it more.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion