scipy core patch

I just committed Daishi's patch to CVS, with Fernando's modification
to catch the new scipy versus old scipy.

Those of you with semi-pristine boxes might want to try it out to make
sure it is working.

One issue: the patch builds either numarray (if found) and
scipy>numeric (if found but not both) with precedence given to
numeric. Shouldn't it be the other way around, with precedence to
scipy_core over Numeric since if someone has the new scipy presumably
it's an upgrade and should take precedence.

I am weakly inclined to support all three rather than one or the other
in the interim, if only because it is a nice way to profile scipy core
versus the old Numeric and because it may be easier to debug what is
going on when we hit user level snags. But since this is only an
interim solution I'm not strongly wedded to any approach.

Please test and report.

Checking in lib/matplotlib/numerix/__init__.py;
/cvsroot/matplotlib/matplotlib/lib/matplotlib/numerix/__init__.py,v <-- __init__.py
new revision: 1.6; previous revision: 1.5

or later.

JDH

John,

I am weakly inclined to support all three rather than one or the other
in the interim, if only because it is a nice way to profile scipy core
versus the old Numeric and because it may be easier to debug what is
going on when we hit user level snags. But since this is only an
interim solution I'm not strongly wedded to any approach.

I agree. I think the testing and transition will be easier if all three are supported for now. I don't see much downside to doing this.

Eric