matplotlib-devel Mailing List for matplotlib

Now that I've got a version of WxMpl that works properly I'd like to 
transition it over to being a matplotlib toolkit. From poking around 
in svn, it looks like the correct thing to do would be to import the 
source directory into '$(SVNROOT)/trunk/toolkits/wxmpl'.
Is that correct?
I'd like to try to get started on version 2.0 before I have my first 
carpal tunnel release surgery in later March. The goals would be:
1. Optional full support for MPL events
2. API for binding user interactions to selection and zoom behavior 
(e.g. "I want right-click selections to zoom in and the 'u' key to 
zoom out, like GNUPLOT")
3. API for controlling Axes zoom state
What do you all think would be the best way to do this? Create a 
branch in '$(SVNROOT)/branches' for 1.3 maintenance?
Ken

James,
The scripts in examples/units (and run by backend_driver.py) are broken; 
they have not been updated to match your addition of the new mandatory 
axis argument to convert() and default_units(). Would you fix them, 
please? (While you are in the neighborhood, you might also update the 
methods by switching to the @staticmethod decorator.)
The argument was also missing from the units.py docstring, but I have 
fixed that.
Thank you.
Eric

On Mon, Feb 16, 2009 at 3:21 PM, Gael Varoquaux
<gae...@no...> wrote:
> I am not blaming anyone, just pointing out a non ideal situation. It has
> already improved a lot with the matplotlib guys and the scipy guys
> merging some changes in extensions and publishing the extensions in an
> importable part of their source tree.
In keeping with the spirit of trying to get all of these extension
changes upstream so that we can all eventually stop carrying our own
copies, below is a tiny change I just made to the inheritance diagram
one. This is needed to ensure that the figure is separated from any
surrounding text, since otherwise you get hideous off-screen diagrams
in the rendered PDF.
This has been committed to the nipy trunk already.
Similarly (for the pymvpa crowd), the api autogen code is now a
module, and it also contains a few small fixes, in particular
regarding chapter titles. Feel free to grab and update your copy:
http://bazaar.launchpad.net/~nipy-developers/nipy/trunk/annotate/head%3A/tools/apigen.py
I've been told the gods of numpy/sphinx don't like auto-generated
docs, but I think there's a valid use case for these tools, so
hopefully in the future it will be possible to include them upstream
for us lesser mortals to use. If not, I guess we'll just continue to
carry our copies around :)
Cheers,
f
# diff, inline because it's so trivial:
=== modified file 'doc/sphinxext/inheritance_diagram.py'
--- doc/sphinxext/inheritance_diagram.py	2009年01月30日 02:00:57 +0000
+++ doc/sphinxext/inheritance_diagram.py	2009年02月20日 21:11:38 +0000
@@ -370,7 +370,7 @@
 graph.run_dot(['-Tpdf', '-o%s' % pdf_path],
 name, parts, graph_options={'size': '"6.0,6.0"'})
- return '\\includegraphics{%s}' % pdf_path
+ return '\n\\includegraphics{%s}\n\n' % pdf_path
 def visit_inheritance_diagram(inner_func):
 """