Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

On Tue, Jun 1, 2010 at 6:17 PM, Fernando Perez wrote: > Hi all, > > I just spent some time digging through the matplotlib code, and I see > that the errorbar line width argument isn't passed through to the > underlying call.  In axis.bar, we have this code: > >        if xerr is not None or yerr i

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

On Wed, Jun 2, 2010 at 8:01 AM, John Hunter wrote: > While this is certainly a bug that needs to be fixed (and Eric is > right that these functions are heavily overworked and hairy), there is > a better workaround than the one you tried.  From the errorbar > docstring: Ignore me :-) I had a tem

Re: [matplotlib-devel] Some keys generate tracebacks in the GTK backend

On Jun 1, 2010, at 8:59 AM, João Luís Silva wrote: > Hi, > > Pressing tab, the "Windows" key or the right click key (and maybe > others) on a plot with the GTKAgg or GTK backend causes the following > traceback: > > Traceback (most recent call last): [snip] > File "/usr/lib/python2.5/site

Re: [matplotlib-devel] Some keys generate tracebacks in the GTK backend

On Wed, Jun 2, 2010 at 8:28 AM, Tony S Yu wrote: > > On Jun 1, 2010, at 8:59 AM, João Luís Silva wrote: > > Hi, > > Pressing tab, the "Windows" key or the right click key (and maybe > others) on a plot with the GTKAgg or GTK backend causes the following > traceback: Thanks Tony, committed to svn

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

I am curious as to why bar() should even be acting like errorbar(). As a user, I would expect bar() to do bar graphs and errorbar() to do error bar graphs. Is there some sort of use-case that I am missing where it makes sense to generate errorbars from a bar() function? Ben Root On Wed, Jun 2,

[matplotlib-devel] Fwd: [Matplotlib-users] [mplot3d] change axis background color

This is from the matplotlib-users list. A user noticed that he can not change the background color of a 3d plot with arguments to .savefig(). Is this a bug or is it intentional? Thanks, Ben Root -- Forwarded message -- From: Denis Laxalde Date: Wed, Jun 2, 2010 at 9:42 AM Subje

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

On Wed, Jun 2, 2010 at 9:48 AM, Benjamin Root wrote: > I am curious as to why bar() should even be acting like errorbar().  As a > user, I would expect bar() to do bar graphs and errorbar() to do error bar > graphs.  Is there some sort of use-case that I am missing where it makes > sense to genera

Re: [matplotlib-devel] Fwd: [Matplotlib-users] [mplot3d] change axis background color

On Wed, Jun 2, 2010 at 10:51 AM, Benjamin Root wrote: > This is from the matplotlib-users list.  A user noticed that he can not > change the background color of a 3d plot with arguments to .savefig().  Is > this a bug or is it intentional? > > Thanks, > Ben Root I think it is just that they are i

Re: [matplotlib-devel] Bug rasterized image in pcolor and pcolormesh

On 06/01/2010 05:21 PM, Benjamin Root wrote: > I have finally managed to test against TkAgg, and the faint white lines > do not appear to occur. So, as far as I can tell (no clue about Macs), > the GTKCairo, pdf and svg backends have this display bug. Shall I file > a bug report for this and anot

Re: [matplotlib-devel] Upcoming Debian stable release and matplotlib new release(s)

John Hunter wrote: > > https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.3 I'm running Fedora 13, and it mostly works but the config output says that Tkinter isn't there, but it is. It finds Qt4 OK, but seems to have trouble finding tkinter and agg. I just did the yum

Re: [matplotlib-devel] Upcoming Debian stable release and matplotlib new release(s)

On Wed, Jun 2, 2010 at 12:34 PM, Tom Holroyd (NIH/NIMH) [E] wrote: > > > John Hunter wrote: >> >> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.3 > > I'm running Fedora 13, and it mostly works but the config output says that > Tkinter isn't there, but it is. It finds

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

On 06/01/2010 03:33 PM, Fernando Perez wrote: > On Tue, Jun 1, 2010 at 4:35 PM, Eric Firing wrote: >> it seems to me that the solution is for >> bar to take a kwarg, say "errorkw", which is a dict that will be passed >> to errorbar via **errorkw, and that can have any valid errorbar kwargs >> in i

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

On Wed, Jun 2, 2010 at 10:26 AM, John Hunter wrote: > On Wed, Jun 2, 2010 at 9:48 AM, Benjamin Root wrote: > > I am curious as to why bar() should even be acting like errorbar(). As a > > user, I would expect bar() to do bar graphs and errorbar() to do error > bar > > graphs. Is there some sor

Re: [matplotlib-devel] Bug rasterized image in pcolor and pcolormesh

On Wed, Jun 2, 2010 at 11:41 AM, Eric Firing wrote: > On 06/01/2010 05:21 PM, Benjamin Root wrote: > > I have finally managed to test against TkAgg, and the faint white lines > > do not appear to occur. So, as far as I can tell (no clue about Macs), > > the GTKCairo, pdf and svg backends have th

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

On 06/02/2010 01:20 PM, Benjamin Root wrote: > > > On Wed, Jun 2, 2010 at 10:26 AM, John Hunter > wrote: > > On Wed, Jun 2, 2010 at 9:48 AM, Benjamin Root > wrote: > > I am curious as to why bar() should even be acting like > erro