On Sep 30, 2010, at 11:46 AM, Benjamin Root wrote: > I just had another thought.... have you ever modified your matplotlibrc file? > It might be possible that you have turned off holds (which is default). If > so, then this would be a bug, because the errorbar function should > temporarially turn on the hold in order to complete its task.
You are correct, I have modified axes.hold to be False by default. For the record, this is with version 0.99.1.1 but has been the case for at least several versions earlier, and I believe is the same on 1.0. On Sep 30, 2010, at 11:48 AM, Eric Firing wrote: > That is a major bug in errorbar. I suspect no one has brought it to our > attention before because hold=True is the default. The only workaround > is what you have already found: ensure hold is True for the call to > errorbar. > > If there is no reply within a couple of days to the effect that someone > has fixed this bug, then please file a ticket so that we don't forget > about it. http://sourceforge.net/tracker/?group_id=80706&atid=560720 > Ok, I'm glad at least for the confirmation that I'm not crazy. I'll add a ticket in a bit if it isn't fixed before then. I guess the fix is simply to enable holds after the first plot command within errorbar(), then restore the hold state at the end. joey ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
