matplotlib change?

[bill.janssen at gmail.com]

On Thursday, June 22, 2017 at 11:24:53 AM UTC-7, Michael F. Stemper wrote:
> On 2017-06-22 12:56, bill.janssen at gmail.com wrote:
> > On Thursday, June 22, 2017 at 10:14:21 AM UTC-7, Michael F. Stemper wrote:
> >> On 2017-06-22 09:50, breamoreboy at gmail.com wrote:
> >>> On Thursday, June 22, 2017 at 3:33:36 PM UTC+1, Michael F. Stemper wrote:
> >
> 
> >>>> Is it likely that the difference in plots due to something that
> >>>> changed in matplotlib between 2.7.12 and 2.7.13? If so, is there
> >>>> some argument that I could specify in one of the functions to
> >>>> prevent this padding/margin/waste? Is there a separate function
> >>>> to call?
> >>>>
> >>>> If the difference isn't due to a change in matplotlib, would it be
> >>>> something OS-dependent? How can I track it down?
> >>
> >>> Id check to see which matplotlib versions you have rather than the Python version.  Either:-
> >>
> >> Okay, that was easy enough:
> 
> >>   >>> import matplotlib
> >>   >>> matplotlib.__version__
> >> '2.0.0'
> >>   >>>
> >>
> >> What's my next step?
> 
> > There were a number of changes to line-drawing in the bump from 1 to 2 -- I found that some of them were not listed in the change notes.  It's worth reviewing https://matplotlib.org/users/dflt_style_changes.html#plotting-functions.
> 
> That nailed it! This section:
> <https://matplotlib.org/users/dflt_style_changes.html#plot-layout>
> addressed my exact problem.
> 
> (Unfortunately, the parameters are not back-compatible, but at least
> I'll be ready when they upgrade the box where I usually work.)
> 
> Thanks for your help.
> 
> BTW, your name is familiar. Were you ever at PARC?
> 
> -- 
> Michael F. Stemper
> This post contains greater than 95% post-consumer bytes by weight.

Still am.

Bill