Travis Oliphant wrote:
> In order to install new and old scipy you will definitely need to
> install one of them to another location besides site-packages (probably
> new scipy).
> Then you will need to make sure your sys.path is set up properly to find
> the scipy you are interested in using for that session.
It sounds like SciPy could use a versioning scheme much like wxPythons:
import wxversion
wxversion.select("2.6")
import wx
See:
http://wiki.wxpython.org/index.cgi/MultiVersionInstalls
In fact, you could probably just grab the wxPython code and tweek it a
little for SciPy.
This was debated a lot on the wxPython lists before being implemented.
After all you could "Just" write a few start-up scripts that manipulate
PYTHONPATH, or re-name some directories, or put in a few sym links,
or, or, or... Also, ideally wxPython major versions are compatible, etc,
etc.
However, when all was said and Dunn, this is a very nice system that
works the same way on all platforms, and doesn't get in the way of
anything. New versions get installed as the default, so if you never use
wxversion, you never know it's there. If you do, then you can test new
versions without having to break any old, running utilities, etc.
Also, the infrastructure is in place for future major version changes, etc.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov