Re: [matplotlib-devel] Handle 'none' as edgecolor for bar()

2010-08-12 Thread Ben North
Ben Root: >Ben North: >> Same kind of thing with >> the kwarg 'color' instead of 'edgecolor', which is also fixed in my >> second recent email. > > Looking through the code for bar(), I see the same thing occurs for the > 'color' keyword

Re: [matplotlib-devel] Handle 'none' as edgecolor for bar()

2010-08-09 Thread Ben North
>> I tried to use "edgecolor = 'none'" in a call to bar(), hoping to get no >> border to the bars, but instead got no bars at all. > > Just to note, the documentation does specify a difference between None and > 'none'. None means to use the rcdefaults and 'none' means no color at all. > Is bar()

[matplotlib-devel] Handle 'none' as edgecolor for bar()

2010-08-09 Thread Ben North
Hi, I tried to use "edgecolor = 'none'" in a call to bar(), hoping to get no border to the bars, but instead got no bars at all. The patch below (against 1.0.0) seems to fix this; it adds a check for 'none' to the existing check for None as a special case of the edgecolor argument. Thanks, Ben.

[matplotlib-devel] Fixing 'FIXME' in bar()

2010-08-09 Thread Ben North
Hi, While looking at axes.py for the color/edgecolor patch just sent, I noticed the FIXME suggesting ValueError instead of assert. Is the below the kind of thing? Ben. --- ORIG-axes.py2010-07-06 15:43:35.0 +0100 +++ NEW-axes.py 2010-08-09 09:43:30.000257000 +0100 @@ -4589,15

[matplotlib-devel] Handle 'none' as color and edgecolor for bar()

2010-08-09 Thread Ben North
Hi, Update to my recent email: perhaps it would make sense to handle the 'color' argument in the same way, allowing hollow bars. Combined patch below. Ben. --- ORIG-axes.py2010-07-06 15:43:35.0 +0100 +++ NEW-axes.py 2010-08-09 09:39:44.000256000 +0100 @@ -4575,15 +4575,17 @@

[matplotlib-devel] XAxis/YAxis set_ticks_position() behaviour

2010-07-15 Thread Ben North
Hi, Firstly, excellent to see matplotlib reach its 1.0 release! I came across an inconsistency in the way XAxis and YAxis behave in the set_ticks_position() method. If you remove the X-axis ticks with my_axes.xaxis.set_ticks_position('none') it leaves the labels alone, whereas if you do th

Re: [matplotlib-devel] Matplotlib-devel Digest, Vol 29, Issue 19

2008-10-20 Thread Ben North
Hope nobody minds if I jump into this discussion: > Date: Mon, 20 Oct 2008 07:55:06 -0500 > From: "John Hunter" <[EMAIL PROTECTED]> > > [...] could you tell us why you prefer or require backend wx over wxagg? I tend to use matplotlib over an X connection, because the data I'm working with is on a

[matplotlib-devel] Patch for PostScript backend

2007-11-20 Thread Ben North
Hi, I think there is a bug in the PostScript backend, when trying to draw a polygon with zero linewidth. If you have a zero linewidth, the generated PostScript is along the lines of 173.31 49.274 m 305.066 57.999 l 173.533 46.684 l closepath gsave fill grestore whereas if t

[matplotlib-devel] Removal of code duplication in axes.py

2007-07-18 Thread Ben North
Hi, I wrote (on -users, but have moved the discussion here to -devel): > > I was wondering, though, whether there'd be any support for some work > > which tidied up the near-duplicate code in axes.py. John Hunter replied: > Certainly, but probably not using meta-classes. > [...] > I'm disinclined