On 7/10/06, Bryce Hendrix <[EMAIL PROTECTED]> 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_whe
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.
On 7/9/06, Bill Baxter <[EMAIL PROTECTED]> wrote:
> 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
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 thenrename the directory containing 0.9.8 to numpySTOP. Then you don'thave to worry about the ordering of the path.The only thing is that the numpy install
On 7/9/06, Bill Baxter <[EMAIL PROTECTED]> 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 nump
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 r
