On Thu, May 31, 2007 at 09:33:49AM -0500, John Hunter wrote:
> A colleague of mine is trying to update our production environment
> with the latest releases of numpy, scipy, mpl and ipython, and is
> worried about the lag time when there is a new numpy and old scipy,
> etc... as the build progresse
Ah, yes, I was typing too fast, thinking too little.
On 5/31/07, John Hunter <[EMAIL PROTECTED]> wrote:
> On 5/31/07, Matthew Brett <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > > That would get them all built as a cohesive set. Then I'd repeat the
> > > installs without PYTHONPATH:
> >
> > Is that
On 5/31/07, Matthew Brett <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > That would get them all built as a cohesive set. Then I'd repeat the
> > installs without PYTHONPATH:
>
> Is that any different from:
> cd ~/src
>cd numpy
>python setup.py build
>cd ../scipy
>python setup.py build
We
Hi,
> That would get them all built as a cohesive set. Then I'd repeat the
> installs without PYTHONPATH:
Is that any different from:
cd ~/src
cd numpy
python setup.py build
cd ../scipy
python setup.py build
...
cd ../numpy
python setup.py install
cd ../scipy
python setup.py
A colleague of mine is trying to update our production environment
with the latest releases of numpy, scipy, mpl and ipython, and is
worried about the lag time when there is a new numpy and old scipy,
etc... as the build progresses. This is the scheme he is considering,
which looks fine to me, but
