never mind (re: loglog problem)

I keep forgetting that unless the clf() is done, that all

    > the previous data elements are still present. And thus the
    > error will repeat. (Waiting for that feature to allow
    > autoclearing in interactive mode I guess)

I added a hold command and axes.hold property to matplotlibrc. In
CVS.

Next release is due out in a day or two (a couple of small bugs to
squash). If any of you can test CVS that would be great - there have
been a lot of changes since 0.53 that touch virtually every part of
matplotlib (see the CHANGELOG in the sdist). Here is a snapshot if
you don't have ready CVS access
http://nitace.bsd.uchicago.edu:8080/files/share/matplotlib-0.54c.tar.gz
- sorry no win32 snapshots at the ready.

Todd, do you still want to build a numarray version? If so, I'll send
you an sdist that I use to build my system and you can build for
numarray and send me back the exe.

JDH

Yes. Please send me the sdist.

Todd

···

On Mon, 2004-05-17 at 18:48, John Hunter wrote:

    > I keep forgetting that unless the clf() is done, that all
    > the previous data elements are still present. And thus the
    > error will repeat. (Waiting for that feature to allow
    > autoclearing in interactive mode I guess)

I added a hold command and axes.hold property to matplotlibrc. In
CVS.

Next release is due out in a day or two (a couple of small bugs to
squash). If any of you can test CVS that would be great - there have
been a lot of changes since 0.53 that touch virtually every part of
matplotlib (see the CHANGELOG in the sdist). Here is a snapshot if
you don't have ready CVS access
http://nitace.bsd.uchicago.edu:8080/files/share/matplotlib-0.54c.tar.gz
- sorry no win32 snapshots at the ready.

Todd, do you still want to build a numarray version? If so, I'll send
you an sdist that I use to build my system and you can build for
numarray and send me back the exe.