[matplotlib-devel] Source tarball should not include setup.cfg (was: 0.99.1.1 build attempts to import non-existing wx)

2009-10-27 Thread Jouni K . Seppänen
Erin Sheldon writes: > I just downloaded 0.99.1.1 and I'm finding this error: > wxPython: no > * wxPython not found > Traceback (most recent call last): > File "setup.py", line 146, in > import wx > ImportError: No module named wx This is because the

Re: [matplotlib-devel] mpl_toolkit.axes_grid default axes class should be changed?

2009-10-27 Thread Pauli Virtanen
Hi! ti, 2009-10-27 kello 15:36 -0400, Jae-Joon Lee kirjoitti: > Thanks for your suggestion and the patch. > However, I'm not very inclined to make such a change any time soon, > since that custom axes class is one of my primary motivation > (supporting the cuvelinear grid) behind the axes_grid too

Re: [matplotlib-devel] mpl_toolkit.axes_grid default axes class should be changed?

2009-10-27 Thread Jae-Joon Lee
Thanks for your suggestion and the patch. However, I'm not very inclined to make such a change any time soon, since that custom axes class is one of my primary motivation (supporting the cuvelinear grid) behind the axes_grid toolkit. And other part of axes_grid toolkit depends on this behavior. On

[matplotlib-devel] mpl_toolkit.axes_grid default axes class should be changed?

2009-10-27 Thread Pauli Virtanen
Hi, mpl_toolkit.axes_grid.AxesGrid uses a custom axes type as the default type of axes it creates. I think it might be more user-friendly to use matplotlib.axes.Axes as the default -- the functionality in basic use seems to be the same. The custom axes handle drawing ticks quite differently fr