breakage

Norbert,

In addition to the problem that numerix was supposed to retain support for Numeric and numarray for the time being, for external use, there is the problem that all examples are currently broken.

Please let me know if you are still online (I know it is very late in Germany); otherwise I may have to revert your changes until the problems are fixed.

Thanks.

Eric

Norbert,

Cancel my last message. I panicked. It looks like the problem with my attempt to run backend_driver.py was that your changes required deletion of the build directory and/or previous matplotlib installation; after doing that, backend_driver.py runs.

The comment about numerix is still valid, so unless John or someone else contradicts me I request that you restore the original numerix, or something like it, so that users' external code can still use numerix to deal with Numeric and/or numarray code and arrays. This is not urgent, but should be done within a day or two to prevent confusion and surprises.

Thanks, and I'm sorry for my excessive and erroneous earlier reaction.

Eric

Eric Firing wrote:

···

Norbert,

In addition to the problem that numerix was supposed to retain support for Numeric and numarray for the time being, for external use, there is the problem that all examples are currently broken.

Please let me know if you are still online (I know it is very late in Germany); otherwise I may have to revert your changes until the problems are fixed.

Thanks.

Eric

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
matplotlib-devel List Signup and Options

Hi Eric,

···

On Thursday 19 July 2007 02:10:03 pm Eric Firing wrote:

unless John or someone else
contradicts me I request that you restore the original numerix, or
something like it, so that users' external code can still use numerix to
deal with Numeric and/or numarray code and arrays.

I thought we were dropping support for numeric and numarray in numerix,
starting with 0.91?

Darren Dale wrote:

Hi Eric,

unless John or someone else
contradicts me I request that you restore the original numerix, or
something like it, so that users' external code can still use numerix to
deal with Numeric and/or numarray code and arrays.

I thought we were dropping support for numeric and numarray in numerix, starting with 0.91?

Not quite. I think the idea was to use numpy internally, but to let the numerix layer stay as it is so that users' code built on numerix can still work with other array packages. When that code calls mpl, everything should still work; the other arrays will internally be converted to numpy.

The point is that although users will have to *have* numpy, they will not yet have to convert all their other packages to numpy; if they have extension packages built on numarray, for example, and accessed via code using matplotlib.numerix, everything will still work.

Eric

···

On Thursday 19 July 2007 02:10:03 pm Eric Firing wrote:

Eric, since it looks like you have not reverted these changes, I went
ahead and did so because svn remains broken. Norbert, thanks for
taking the lead on numpifying some of the modules, but as Eric said,
we plan on keeping the numerix layer for sometime since a lot of
external code depends on it. Apparently your changes broke the
numerix layer, but the rest of mpl still depended on it, so I had to
revert them. I had hoped to do an svn diff between HEAD and 3573 (the
last revision before your numerix changes) and manually remove all the
changes in the diff file to just the lib/matplotlib/numerix so the
rest of your and others work would not be lost, and then apply that
diff against 3573. Unfortunately, because you also changed many of
the numerix imports which would be broken against a working numerix, I
had to simply revert to all the python code to 3573 (src code changes
should be OK)

Also, the style we agreed (in the usual case) to use

  import numpy as npy
  npy.ones(something)

rather than

  from numpy import ones.

This is also a good idea to remind developers to run simple demos and
examples/backend_driver.py after non-trivial commits. I usually run
examples/simple_demo.py and the examples/backend_driver.py. . The
latter I don't always run to completion, but if it runs for a while I
feel OK with a commit

Thanks,
JDH

···

On 7/19/07, Eric Firing <efiring@...229...> wrote:

Please let me know if you are still online (I know it is very late in
Germany); otherwise I may have to revert your changes until the problems
are fixed.