matplotlib-users

[Matplotlib-users] axes.set_xticklabels bug?

[Charlie M. <cw...@gm...>]

simple pylab script:

a =3D axes()
a.set_xticklabels(['a', 'b', 'c'])
show()

When I move the mouse around the axes I get this error from the callback:

.......
/usr/local/lib/python2.4/site-packages/matplotlib/ticker.py in
__call__(self, x, pos)
    176         'Return the format for tick val x at position pos'
    177         if pos>=3Dlen(self.seq): return ''
--> 178         else: return self.seq[pos]
    179
    180 class FuncFormatter(Formatter):

TypeError: list indices must be integers

"pos" is None

Any ideas?
- Charlie

CVS and at least GTKAgg and TkAgg

Re: [Matplotlib-users] axes.set_xticklabels bug?

[John H. <jdh...@ac...>]

>>>>> "Charlie" == Charlie Moad <cw...@gm...> writes:

    Charlie> simple pylab script: a = axes() a.set_xticklabels(['a',
    Charlie> 'b', 'c']) show()

    Charlie> When I move the mouse around the axes I get this error
    Charlie> from the callback:

    Charlie> .......
    Charlie> /usr/local/lib/python2.4/site-packages/matplotlib/ticker.py
    Charlie> in __call__(self, x, pos) 176 'Return the format for tick
    Charlie> val x at position pos' 177 if pos>=len(self.seq): return
    Charlie> ''
    --> 178 else: return self.seq[pos]
    Charlie>     179 180 class FuncFormatter(Formatter):

    Charlie> TypeError: list indices must be integers

    Charlie> "pos" is None

Did someone fix this?  I can't replicate it.

JDH

[Matplotlib-users] Re: axes.set_xticklabels bug?

[Jouni K S. <jk...@ik...>]

John Hunter <jdh...@ac...> writes:

>>>>>> "Charlie" == Charlie Moad <cw...@gm...> writes:
>
>     Charlie> simple pylab script: a = axes() a.set_xticklabels(['a',
>     Charlie> 'b', 'c']) show()
>
>     Charlie> TypeError: list indices must be integers
>
> Did someone fix this?  I can't replicate it.

I had similar problems with an earlier CVS version (using WXAgg), but
a recent cvs update command fixed it. Perhaps the problem has been
masked instead of fixed, since pylab fails to show the x coordinate of
the mouse pointer when I move it around. That is, the text in the
bottom right panel is something like "x=, y=3.5016e-1". It seems that
the code that caused the exception is related to computing these
coordinates.

-- 
Jouni K Seppänen