[Numpy-discussion] numpy easy_install fails for python 3.2

Ralf Gommers ralf.gommers@googlemail....
Fri Jun 3 10:36:20 CDT 2011


On Wed, May 4, 2011 at 8:51 PM, Matthew Brett <matthew.brett@gmail.com>wrote:

> Hi,
>
> On Wed, May 4, 2011 at 1:23 PM, Ralf Gommers
> <ralf.gommers@googlemail.com> wrote:
> >
> >
> > On Wed, May 4, 2011 at 6:53 PM, Matthew Brett <matthew.brett@gmail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> I can imagine that this is low-priority, but I have just been enjoying
> >> pytox for automated virtualenv testing:
> >>
> >> http://codespeak.net/tox/index.html
> >>
> >> which revealed that numpy download-build-install via easy_install
> >> (distribute) fails with the appended traceback ending in "ValueError:
> >> 'build/py3k/numpy' is not a directory".
> >
> > I think it would be good to just say "wontfix" immediately, rather than
> just
> > leaving a ticket open and not do anything (like we did with
> > http://projects.scipy.org/numpy/ticket/860).
>
> Ouch - yes - I see what you mean.
>
> > It seems tox can also use pip (which works with py3k now), does that work
> > for you?
>
> I think current tox 0.9 uses virtualenv5 for python3.2 and has to use
> distribute, I believe.  Current tip of pytox appears to use virtualenv
> 1.6.1 for python 3.2, and does use pip, but generates the same error
> in the end.
>
> I've appended the result of a fresh python3.2 virtualenv and a "pip
> install numpy".
>
> Sorry - I know these are not fun problems,
>

Not too much fun indeed. Helped me become better friends with pdb though. I
opened http://projects.scipy.org/numpy/ticket/1857 and explained the issue
as far as I understand it. Summary:

   1. There's a bug in Configuration.__init__ where
   dirname(abspath(nonexistingfile)) gives curdir.


   1. The bug in (1) happens to work out well in combination with the
   os.chdir call in the main setup.py.


   1. Once we correct for this so that the bug from (1) does not affect
   install under pip + virtualenv, we run into another issue due to both
   numpy.distutils and pip messing with __file__ in ugly and incompatible
   ways.

Even if the "python setup.py egg_info" command in pip can be fixed, there
may well be more issues to run into. I don't think I'm going to spend more
time on this.

If someone wants a challenge and can wrap his brain around things like:
    caller_file = eval('__file__', frame.f_globals, frame.f_locals)
have fun!

Cheers,
Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20110603/396efea3/attachment-0001.html 


More information about the NumPy-Discussion mailing list