From: Hans D. <han...@ki...> - 2012-08-31 10:10:34
|
: ) Thanks for the response. On 08/30/2012 08:41 PM, Eric Firing wrote: > Submitting patches as github pull requests is strongly preferred. See > http://matplotlib.sourceforge.net/devel/index.html. > > In the svn days, most devel discussions of proposed changes occurred on > this mailing list, but now attention is much more on github PRs and less > on the mailing list. Okay, I will try that then! >> Please allow me to participate. > > We welcome you--but sometimes we are simply overwhelmed and/or > unorganized, and consequently unresponsive. There is a random aspect to it! I can deal with randomness, in fact, the field of statistics is one of my special interests : D > Regarding your patch: this sounds like it might be a good idea, but I > don't think the rc param should be called lines.capsize because it is > not a general line property, but something specific to errorbars. > "lines.*cap*" refer to completely unrelated general line properties. > > It would be good to get some thoughts from others as to whether to an > "errorbar" or similar category should be added to rcParams, with your > suggestion as the first entry in that category. Maybe we need some > policy guideline as to what should go in rcParams and what should not. You are right, I also thought about that. My first idea was to add an errorbar.* category, but then I saw that also the bar plots (axes.bar(...), axes.barh(...)) use caps. What I am trying to say is that it is not only used by axes.errorbar(...). That's why I put into the lines.* category, but that's certainly open for discussion. Having a policy on what to put into rcParams sounds useful. Best regards, Hans |