I've submitted the following:

> http://sourceforge.net/tracker/index.php?

> func=detail&aid=1360855&group_id=80706&atid=560722

> This patch allows one to use matplotlib with (just) the

> new scipy.

Just for clarification, when you say "just" the new scipy, you mean

that it works with Numeric, numarray *and* the new scipy, not that it

works with the new scipy and only the new scipy.

I read over the patch and it looks like you did a very thorough job.

Thanks! In the near term, this means that mpl would compile three

shared object files for each of the three array objects for each

extension module, which of course will increase compile times and

binary distribution sizes. Travis, Perry, Todd and I have been

discussing the benefits of changing matplotlib to work *only* with the

new scipy, which include faster build times, smaller binaries, less

complexity and pushing the community to a single array object. Since

the new array interface works with Numeric 24, recent numarray or the

new scipy, *any* of these array packages would work with a matplotlib

compiled just for scipy. We decided to hold off on doing this until

scipy installations issues were sorted out even on semi-obscure

platforms -- Travis, what's your sense of this?

So my inclination is to include your patch now, during a transition

period, and then move over to a new scipy only build, retaining the

numerix layer so Numeric, numarray and (new) scipy users can continue

to use mpl transparently. In particular we need to make sure that

basemap which uses numarray.ndimage continues to work.

Does this sound like the right approach?

JDH