numpy-discussion

[Numpy-discussion] Testing a self-compiled numpy

[Bill B. <wb...@gm...>]

I got numpy compiled according the the instruction on the Wiki, but is there
some way to try it out without wiping out my stable install of 0.9.8?

I tried modifying my PYTHONPATH to put the new numpy build directory first,
but 'import numpy' still picks up the installed 0.9.8 version.

I also tried running python from the build directory.  Then 'import numpy'
prints out "Running from numpy source directory", but the numpy thus
imported seems not to have any attributes.

Suggestions?
--bill

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

[Keith G. <kwg...@gm...>]

On 7/9/06, Bill Baxter <wb...@gm...> wrote:
> I got numpy compiled according the the instruction on the Wiki, but is there
> some way to try it out without wiping out my stable install of 0.9.8?
>
> I tried modifying my PYTHONPATH to put the new numpy build directory first,
> but 'import numpy' still picks up the installed 0.9.8 version.

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.

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.

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

[Bill B. <wb...@gm...>]

Thanks for the reply Keith.

On 7/10/06, Keith Goodman <kwg...@gm...> 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.
>

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

[Keith G. <kwg...@gm...>]

On 7/9/06, Bill Baxter <wb...@gm...> wrote:
> Thanks for the reply Keith.
>
>
> On 7/10/06, Keith Goodman <kwg...@gm...> 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
> )

Doesn't  --prefix=/install/numpy/here/ work on windows?

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

[Bryce H. <bhe...@en...>]

Keith Goodman wrote:
>> 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
>> )
>>     
>
> Doesn't  --prefix=/install/numpy/here/ work on windows?
>   
For our Windows Enthon project, the build command is

setup.py config --compiler=mingw32 build --compiler=mingw32 install 
--prefix=path_to_where_numpy_goes.

Bryce

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

[Bill B. <wb...@gm...>]

On 7/10/06, Bryce Hendrix <bhe...@en...> wrote:
>
>  Keith Goodman wrote:
>
>  Doesn't  --prefix=/install/numpy/here/ work on windows?
>
> For our Windows Enthon project, the build command is
>
> setup.py config --compiler=mingw32 build --compiler=mingw32 install --
> prefix=path_to_where_numpy_goes.
>

Thanks for the info.  I added it to the "building numpy/scipy on windows"
wiki.

Still looking for help on how to get SciPy to build on Windows if anyone
knows anything about that.  I posted my symptoms to the SciPy list, but got
no response.

--bb