From: John H. <jdh...@ac...> - 2004-03-28 15:52:13
|
>>>>> "Steve" == Steve Chaplin <ste...@ya...> writes: Steve> John, I'm having a problem running the barchart demo, it Steve> reports: Steve> $ python barchart_demo.py Traceback (most recent call Steve> last): File "barchart_demo.py", line 23, in ? legend( Steve> (p1[0], p2[0]), ('Men', 'Women') ) File Steve> "/usr/lib/python2.3/site-packages/matplotlib/matlab.py", Steve> line 765, in legend return gca().legend(*args, **kwargs) Steve> File "/usr/lib/python2.3/site-packages/matplotlib/axes.py", Steve> line 972, in legend self._legend = Legend(self.dpi, Steve> self.bbox, lines, labels, loc) File Steve> "/usr/lib/python2.3/site-packages/matplotlib/legend.py", Steve> line 104, in __init__ self._texts = self._get_texts(labels, Steve> textleft, upper) File Steve> "/usr/lib/python2.3/site-packages/matplotlib/legend.py", Steve> line 206, in _get_texts transy = self.transy, TypeError: Steve> __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 http://sourceforge.net/mailarchive/message.php?msg_id=7544800. 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 |