Gael Varoquaux wrote:
> Hi,
>
> Trying out version 0.87.4 I noticed that the example given on
> pages
> http://matplotlib.sourceforge.net/screenshots/plotmap.py
> and
> http://scipy.org/Cookbook/Matplotlib/Maps
> fail with :
>
> In [1]: from matplotlib.toolkits.basemap import Basemap
> -
On Thursday 27 July 2006 8:33 am, JIM MacDonald wrote:
> Hi,
>
> I've just moved from MATLAB to matplotlib, and I'm really impressed
> with the quality of the PS figures it generates with usetex and the
> xpdf distiller.
Glad to hear it.
> I've hit a couple of problems though
[...]
> The first p
Matplotlib is quite nice, but I keep running into problems with the
actual display interface.
In some cases the plot window freezes and such when using it from a
debugger, or sometimes pylab.show() just never returns. Matlab's
plotting interface just never gave me so much trouble.
I think all the
Darren,
I don't like the default either--I just left it in place so as not to
change too many things at once. There is always some tension in mpl
between doing things the Matlab way, at least by default, and doing
things better. If there is no opinion to the contrary, I am happy to
change co
Due to repeated emails by Eric Firing about how something like this
would be nice to have, I finally got around to packaging a little
utility I wrote. I uploaded it to the MPL source repository. The basic
idea is to create a layout engine for matplotlib. Not wanting to
(re-)invent an API, I decided
John,
I think we really need copy (and maybe deepcopy) functions that work
with all transforms, not just Separable transforms. This looks fairly
easy except for one thing: the transform creation functions return
objects that don't provide any clean way of distinguishing among the
types of tra
