matplotlib-devel Mailing List for matplotlib

John Hunter <jd...@gm...> writes:
> On Sun, Jun 7, 2009 at 8:05 PM, Eric Firing<ef...@ha...> wrote:
>> This looks like a very good idea.
>
> I agree -- the presence of *args and **kwargs in the pyplot
> docstrings, the interface most people use, is a major wart. I suggest
> committing this to HEAD when you are ready to go.
I would like to ask the opinion of other developers before checking it
in. I now have two different implementations in two branches of my
github repository (patches attached):
http://github.com/jkseppan/matplotlib/tree/boilerplate
http://github.com/jkseppan/matplotlib/tree/autoboiler
The first one in an improved boilerplate.py as before, so it can be used
to write a large part of pyplot.py so that the signatures and docstrings
are all in there. I still haven't added any automation to call it while
building matplotlib, but that's something of a separate problem.
The second one is a version of pyplot.py that inspects the methods of
Axes objects and creates corresponding functions automatically. It uses
decorator.py, which I have included with the matplotlib source.
I think I personally like the boilerplate branch better. While the code
is a little hairy, you can see its output in pyplot.py, so if it ever
needs to be modified, there is something to run "diff" on. The code in
the autoboiler branch was more difficult to get right, and it creates
the functions at runtime via "exec" (which is how decorator.py can set
the signature of the functions it creates).
In the autoboiler branch, importing pyplot seems to be very slightly
slower. Here is the average time per example it took to run the examples
in the pylab_examples subdirectory in the three branches using the
template backend, in two different runs:
 master boilerplate autoboiler
run 1 1.013 1.028 1.043
run 2 1.028 1.027 1.043
It looks like there is a difference, but it is as large as the
difference between runs in the master branch; much more careful
experimentation would be needed to be sure about the magnitude of 
the difference.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

I just committed a change to backend_driver.py that allows running a
subset of all tests by directory. In the process I changed the command
line parsing to use OptionParser, but I tried to keep it reasonably
backward compatible. Here are the options the script now takes:
Options:
 -h, --help show this help message and exit
 -d DIRS, --dirs=DIRS, --directories=DIRS
 Run only the tests in these directories; comma-
 separated list of one or more of: pylab (or
 pylab_examples), api, units, mplot3d
 -b BACKENDS, --backends=BACKENDS
 Run tests only for these backends; comma-separated
 list of one or more of: agg, ps, svg, pdf, template,
 cairo, cairo.png, cairo.ps, cairo.pdf, cairo.svg.
 Default is everything except cairo.
 --clean Remove result directories, run no tests
 -c, --coverage Run in coverage.py
 -v, --valgrind Run in valgrind
In addition to the list of backends given via the -b and --backends
options, any extra arguments are added to the list of backends, or
interpreted as switches to pass to the subprocess that runs each test.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks