John, I'm having a problem running the barchart demo, it
> reports:
> $ python barchart_demo.py Traceback (most recent call
> last): File "barchart_demo.py", line 23, in ? legend(
> (p1[0], p2[0]), ('Men', 'Women') ) File
> "/usr/lib/python2.3/site-packages/matplotlib/matlab.py",
> line 765, in legend return gca().legend(*args, **kwargs)
> File "/usr/lib/python2.3/site-packages/matplotlib/axes.py",
> line 972, in legend self._legend = Legend(self.dpi,
> self.bbox, lines, labels, loc) File
> "/usr/lib/python2.3/site-packages/matplotlib/legend.py",
> line 104, in __init__ self._texts = self._get_texts(labels,
> textleft, upper) File
> "/usr/lib/python2.3/site-packages/matplotlib/legend.py",
> line 206, in _get_texts transy = self.transy, TypeError:
> __init__() got an unexpected keyword argument 'fontsize'
Hi Steve - you're running CVS right?
Font management is undergoing a thorough overhaul. Paul Barrett has
written a free standing, platform independent, font-finder (no
ttfquery or FontTools dependency) and we're still working out the
bugs. Basically, all the font dict and font kwargs examples are
currently broken in CVS, but Paul is aware of this and will probably
have it cleaned up in a couple of days.
The nice thing about the new design is it will enable specifying fonts
in a way that will work across backends and platforms using a naming
scheme and font finder algorithm that is based on the W3C Cascading
Style Sheet specification. See the thread
[Lksctp-developers] sctperf v.0.1 | Linux Kernel SCTP.
If you plan to work with the CVS version, I recommend subscribing to
the devel list so you can get a heads up on these issues. Generally
we try to keep a working version in CVS, but if you on the bleeding
edge.....
JDH