matplotlib-devel Mailing List for matplotlib

Hi,
In the last couple of days, the daily builds on Launchpad have been
choking on the docs. They get to "reading sources... [ 91%]
faq/howto_faq", then seemingly lock up until the queue manager aborts
the build. It claims there's 2h30 of inactivity before that happens,
so it looks like something really is wrong.
Example build log:
https://launchpadlibrarian.net/102978621/buildlog_ubuntu-precise-i386.matplotlib_1.1.0%2B6017%2B10%7Eprecise1_FAILEDTOBUILD.txt.gz
It appears to be this big commit which broke it (unless it was an
external factor like some change to Sphinx):
https://github.com/matplotlib/matplotlib/commit/76665d059523cf0b89695570dc311ce8b50d4a4b
Has anyone else seen this, or do you have any ideas what might be causing it?
Thanks,
Thomas
P.S. Apologies to anyone getting this twice.

On Tue, Apr 24, 2012 at 7:49 AM, Mike Kaufman <mc...@gm...> wrote:
> If mew=0, then the caps on errorbars are not drawn regardless of the
> setting of the "capsize" option. I don't think this should be the
> behavior, it certainly caught me off guard, since I had mew=0 set in
> rcParams.
>
> This is present as of 5b499f0180befea04fab7bfda17ba3ad7cf2380e
> (Mar 22nd master)
>
> M
>
>
This is indeed confusing and I have been meaning to do something about this
for a while now (yet another item in my todo list...). Keep in mind that
there is actually no discrepancy. The marker is turned onto its side. So
the marker edge width parameter actually effects the cap's thickness. So,
having a finite capsize, but a zero thickness should result in no cap being
drawn.
But it is totally unintuitive that mew should have anything to do with the
cap thickness and what should be done is introduce a new kwarg "capthick"
or "capheight" and eventually have it completely replace the responsibility
of mew in errorbars.
Ben Root

On Thu, Apr 19, 2012 at 3:04 AM, Jae-Joon Lee <lee...@gm...> wrote:
> I think what we may do is to make the default value of "scatterponts"
> to None, and if None, set it to the value of numpoints.
> But, I want to hear how others think about it.
>
> Regards,
>
> -JJ
>
>
I think that would be reasonable. And maybe put "scatterpoints" onto a
deprecation path?
Cheers!
Ben Root

yep, it works. Thanks for fixing it so quickly!
On 23.04.2012 23:34, Michael Droettboom wrote:
> Git bisect shows that this was introduced in f57dddc20625. Looking at
> the github comments for that commit:
>
> https://github.com/matplotlib/matplotlib/commit/f57dddc20625809436956675d23b09baddcc9e0e
>
>
> strange enough the problem and solution are already discussed, it just
> seems the solution never made it in.
>
> This should now be fixed in 48c31f7ff660
>
> Mike
>

If mew=0, then the caps on errorbars are not drawn regardless of the 
setting of the "capsize" option. I don't think this should be the 
behavior, it certainly caught me off guard, since I had mew=0 set in 
rcParams.
This is present as of 5b499f0180befea04fab7bfda17ba3ad7cf2380e
(Mar 22nd master)
M