matplotlib-devel Mailing List for matplotlib

On Wed, Oct 10, 2012 at 7:36 PM, Benjamin Root <ben...@ou...> wrote:
> Looks like github has changed the layout of the default landing page for any
> github account. This now has the account's profile image shown much larger
> than originally intended. Our front page now has a very pixelated logo on
> display. Given how much we pride ourselves on high-quality images, we
> should probably fix this:
>
> https://github.com/matplotlib
>
> Cheers!
> Ben Root
This has been bugging me for a while...
-- 
Damon McDougall
http://www.damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom

Hi Ben,
Seems like github is down at the moment, and I wanted to relay something I
> have noticed in some of the PEP8 changes:
>
I'm guessing it's on one of my PR
>
> "The preferred place to break around a binary operator is *after* the
> operator, not before it."
>
I am seeing some proposed changes that would put the binary operator on the
> next line (particularly in backend_bases.py).
>
That's an artifact of autopep8 which I use on the big files to correct the
pep8 problems.
If you could be more precised of which PR and which line this problem
occurs, I can fix it.
Thanks,
Nelle
> Cheers!
> Ben Root
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Seems like github is down at the moment, and I wanted to relay something I
have noticed in some of the PEP8 changes:
"The preferred place to break around a binary operator is *after* the
operator, not before it."
I am seeing some proposed changes that would put the binary operator on the
next line (particularly in backend_bases.py).
Cheers!
Ben Root

Looks like github has changed the layout of the default landing page for
any github account. This now has the account's profile image shown much
larger than originally intended. Our front page now has a very pixelated
logo on display. Given how much we pride ourselves on high-quality images,
we should probably fix this:
https://github.com/matplotlib
Cheers!
Ben Root

On 2012年10月09日 4:38 PM, Benjamin Root wrote:
>
>
> On Tuesday, October 9, 2012, Mike Kaufman wrote:
>
> On 10/9/12 9:42 PM, Eric Firing wrote:
> > On 2012年10月09日 3:03 PM, Mike Kaufman wrote:
>
> >> clf()
> >> x = arange(10)
> >> subplot(211)
> >> plot(x, x)
> >> tick_params(right='off') # works.
> >>
> >> subplot(212)
> >> semilogy(x, x)
> >> tick_params(right='off') # doesn't work!
> >> draw()
> >
> >
> > You need to specify an additional kwarg, which='both'. The default is
> > "major" only, but log axes use minor and major ticks.
>
> You are so right. And now that I think about it, this has bitten me (and
> been solved by me) before. And I think the reason has got to be that the
> regular plot simply doesn't have any minor ticks by default. That's
> bugged me because (correct me if I'm wrong) many of our competitors'
> (e.g. Matlab, IDL) plots do have minor ticks as a default.
>
> What do you think about changing the default of tick_params to 'both',
> and perhaps add minor ticks (I suggest a single minor between each
> major) to regular plots as a default?
>
> M
>
>
>
> I'd +1 that MEP. Though, a place where it might not makes sense is bar
> charts. Something to think about.
I would not support making minor ticks appear by default on linear axes. 
 I don't think Matlab does it; but more importantly, (1) doing a good 
job of automatic tick location would get more difficult, and (2) minor 
ticks on linear axes are usually visual clutter, not good design.
Regarding defaulting to "both", the problem is that this would make 
sense only for some of the parameters. For example, one would not want 
"both" to be the default when setting tick length, and might not want it 
when setting width. Granted, there are more options that one typically 
would want to apply to both than that one would not, so "both" might 
still be a better default.
Eric
>
> Ben Root
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Tuesday, October 9, 2012, Mike Kaufman wrote:
> On 10/9/12 9:42 PM, Eric Firing wrote:
> > On 2012年10月09日 3:03 PM, Mike Kaufman wrote:
>
> >> clf()
> >> x = arange(10)
> >> subplot(211)
> >> plot(x, x)
> >> tick_params(right='off') # works.
> >>
> >> subplot(212)
> >> semilogy(x, x)
> >> tick_params(right='off') # doesn't work!
> >> draw()
> >
> >
> > You need to specify an additional kwarg, which='both'. The default is
> > "major" only, but log axes use minor and major ticks.
>
> You are so right. And now that I think about it, this has bitten me (and
> been solved by me) before. And I think the reason has got to be that the
> regular plot simply doesn't have any minor ticks by default. That's
> bugged me because (correct me if I'm wrong) many of our competitors'
> (e.g. Matlab, IDL) plots do have minor ticks as a default.
>
> What do you think about changing the default of tick_params to 'both',
> and perhaps add minor ticks (I suggest a single minor between each
> major) to regular plots as a default?
>
> M
>
>
>
I'd +1 that MEP. Though, a place where it might not makes sense is bar
charts. Something to think about.
Ben Root

On 10/9/12 9:42 PM, Eric Firing wrote:
> On 2012年10月09日 3:03 PM, Mike Kaufman wrote:
>> clf()
>> x = arange(10)
>> subplot(211)
>> plot(x, x)
>> tick_params(right='off') # works.
>>
>> subplot(212)
>> semilogy(x, x)
>> tick_params(right='off') # doesn't work!
>> draw()
>
>
> You need to specify an additional kwarg, which='both'. The default is
> "major" only, but log axes use minor and major ticks.
You are so right. And now that I think about it, this has bitten me (and 
been solved by me) before. And I think the reason has got to be that the 
regular plot simply doesn't have any minor ticks by default. That's 
bugged me because (correct me if I'm wrong) many of our competitors' 
(e.g. Matlab, IDL) plots do have minor ticks as a default.
What do you think about changing the default of tick_params to 'both', 
and perhaps add minor ticks (I suggest a single minor between each 
major) to regular plots as a default?
M

On 2012年10月09日 3:03 PM, Mike Kaufman wrote:
>
> The example code should explain the problem.
> tick_params(), at least for the ticks themselves, is ignored by log plots.
>
> clf()
> x = arange(10)
> subplot(211)
> plot(x, x)
> tick_params(right='off') # works.
>
> subplot(212)
> semilogy(x, x)
> tick_params(right='off') # doesn't work!
> draw()
You need to specify an additional kwarg, which='both'. The default is 
"major" only, but log axes use minor and major ticks.
Eric
>
> M
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

The example code should explain the problem.
tick_params(), at least for the ticks themselves, is ignored by log plots.
clf()
x = arange(10)
subplot(211)
plot(x, x)
tick_params(right='off') # works.
subplot(212)
semilogy(x, x)
tick_params(right='off') # doesn't work!
draw()
M