Installing numpy with setupegg.py does indeed install numpy as an egg, but it does not solve the problem I describe here (tested with numpy-1.3.0rc1, and the rest as described below). If numpy is listed as a dependency for another package which is installed into a virtual environment, setuptools tries to download and install numpy instead of just adjusting the easy_install.pth file.
Hmm. I tried to install my packages without a virtual environment, and that works ok. So it must be a problem in the interaction between setuptools and virtualenv... I'll cross post this in the virtualenv mailing list...
----- "David Cournapeau" firstname.lastname@example.org wrote:
Christian Marquardt wrote:
I've run into the following problem:
To me, that's a bug, but I would like to know if it is a bug in numpy (which might not support setuptools in the correct way) or setuptools which tries to install an already existing package.
If you want setuptools 'support', I think you should install numpy through the setupegg.py script.
-- Dr. Christian Marquardt Email: email@example.com Wilhelm-Leuschner-Str. 27 Tel.: +49 (0) 6151 95 13 776 64293 Darmstadt Mobile: +49 (0) 179 290 84 74 Germany Fax: +49 (0) 6151 95 13 885