UnboundLocalError from multiple traces with plot_date in 0.90

I'm back to developing with matplotlib after a bit of a hiatus. I am
refactoring an app I wrote about two years ago. I suspect I have uncovered
a bug in 0.90 which was not present in 0.87.7. The small test script,
which I created to reproduce the problem, fails with the follow traceback
in 0.90:

ddf@...1473...:blush: python debug.py
Traceback (most recent call last):
  File "debug.py", line 43, in ?
    plot_date(jt2, f2, ':')
  File "/usr/lib/python2.4/site-packages/matplotlib/pylab.py", line
2064, in plot_date
    ret = gca().plot_date(*args, **kwargs)
  File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line 2395,
in plot_date
    self.xaxis_date(tz)
  File "/usr/lib/python2.4/site-packages/matplotlib/axes.py", line 1564,
in xaxis_date
    formatter = AutoDateFormatter(locator)
UnboundLocalError: local variable 'locator' referenced before assignment

but running in 0.87.7 produces a figure with two traces. If only one
trace is done, 0.90 produces a figure.

I can drop back to 0.87.7 but I would prefer to continue working with 0.90.

Glad to be back using Python and matplotlib!

I'm running on Debian Etch on both machines. 0.90 is compiled from the latest
tarball since Etch only has 0.87.7 available.

                                   Delbert

debug.zpi (985 Bytes)

Yes, I discovered that myself yesterday -- fixed in svn.

Thanks for the report.

JDH

···

On 2/15/07, Delbert Franz <ddf@...479...> wrote:

I'm back to developing with matplotlib after a bit of a hiatus. I am
refactoring an app I wrote about two years ago. I suspect I have uncovered
a bug in 0.90 which was not present in 0.87.7. The small test script,
which I created to reproduce the problem, fails with the follow traceback
in 0.90: