matplotlib-devel Mailing List for matplotlib

Hi,
I just wanted to say that I like the current matplotlib's (0.98.1)
line thickness and colors.
I don't know what exactly has changed since before, but the figures
now look really great. It's a pleasure to look at it. Thanks!
Ondrej

Yes, I believe so, barring any other side effects we inadvertently 
create in the future... ;)
Mike
Darren Dale wrote:
> On Monday 07 July 2008 02:33:40 pm Michael Droettboom wrote:
> 
>> Fernando Perez wrote:
>> 
>>> On Mon, Jul 7, 2008 at 10:28 AM, Michael Droettboom <md...@st...> 
>>> 
> wrote:
> 
>>>> Thank you for finding this! That is indeed the case.
>>>>
>>>> I think we need to rework the plot generation code to avoid side effects
>>>> by forcibly resetting state between plots. Maybe we should just fork
>>>> another Python process for each plot. Darren, since (I believe) you
>>>> wrote the initial documentation plotting code, do you have any thoughts?
>>>> 
>>> Isn't that unnecessarily slow? Why not have each plot simply make a
>>> call to load a clean state? rc_defaults() or somesuch? This little
>>> call could even be auto-run by the doc generation code, without
>>> requiring a full process restart.
>>> 
>> Agreed, and that does seem to fix this particular issue.
>> 
>
> Sorry I didn't respond before now, I got back into town last night. Tony, 
> thank you for tracking this down, that was a really good find. I don't think 
> I would have ever thought to look in the right place. 
>
> Mike, is the issue settled?
>
> Darren
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Monday 07 July 2008 02:33:40 pm Michael Droettboom wrote:
> Fernando Perez wrote:
> > On Mon, Jul 7, 2008 at 10:28 AM, Michael Droettboom <md...@st...> 
wrote:
> >> Thank you for finding this! That is indeed the case.
> >>
> >> I think we need to rework the plot generation code to avoid side effects
> >> by forcibly resetting state between plots. Maybe we should just fork
> >> another Python process for each plot. Darren, since (I believe) you
> >> wrote the initial documentation plotting code, do you have any thoughts?
> >
> > Isn't that unnecessarily slow? Why not have each plot simply make a
> > call to load a clean state? rc_defaults() or somesuch? This little
> > call could even be auto-run by the doc generation code, without
> > requiring a full process restart.
>
> Agreed, and that does seem to fix this particular issue.
Sorry I didn't respond before now, I got back into town last night. Tony, 
thank you for tracking this down, that was a really good find. I don't think 
I would have ever thought to look in the right place. 
Mike, is the issue settled?
Darren