Re: [Numpy-discussion] Testing a self-compiled numpy

[Bill Baxter]

Thanks for the reply Keith.

On 7/10/06, Keith Goodman <[EMAIL PROTECTED]> wrote:

One quick hack is to install the new numpy somewhere else and then
rename the directory containing 0.9.8 to numpySTOP. Then you don't
have to worry about the ordering of the path.

The  only thing is that the numpy installer built by the windows instructions on the Wiki doesn't give you an option of where to install numpy.  It installs straight to {PYTHON_DIR}\lib\site-packages\numpy.  (The command suggested by the wiki is:

c:\path\to\python.exe setup.py config --compiler=mingw32 build --compiler=mingw32 bdist_wininst
)

But yeh, in a similar vein I can just rename the current numpy directory to numpy_98 or something like that before installing, and that seems to work.

I just thought there would be a more sophisticated way to test various verisons of modules in Python than renaming directories.

I install in /usr/local/scipy/numpy (then it is easy to remove numpy
without worrying about leaving behind any files) and then I create the
file /usr/lib/python2.4/site-packages/addlocalpath.pth that contains
the lines:

/usr/local/scipy/scipy/lib/python2.4/site-packages/
/usr/local/scipy/numpy/lib/python2.4/site-packages/

Then there is no need to play with the path.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion