Re: [matplotlib-devel] Example images broken in docs

2008-07-08 Thread Michael Droettboom
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 <[EMAIL PROTECTED]>

Re: [matplotlib-devel] Example images broken in docs

2008-07-08 Thread Darren Dale
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 <[EMAIL PROTECTED]> wrote: > >> Thank you for finding this! That is indeed the case. > >> > >> I think we need to rework the plot generation code to avoid s

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Michael Droettboom
Fernando Perez wrote: > On Mon, Jul 7, 2008 at 10:28 AM, Michael Droettboom <[EMAIL PROTECTED]> 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

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Fernando Perez
On Mon, Jul 7, 2008 at 10:28 AM, Michael Droettboom <[EMAIL PROTECTED]> 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 Pytho

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Michael Droettboom
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 documentati

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Michael Droettboom
Removing all contents of the doc/matplotlibrc and doc/pyplots/matplotlibrc files (reverting to the defaults), or removing the files completely, does not fix the tick outside the axes issue... Removing my ~/.matplotlib/matplotlibrc does not resolve the issue. However, other rcparam values do c

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Tony Yu
On Jul 7, 2008, at 12:19 PM, Michael Droettboom wrote: > I noticed today that the examples in the docs have the ticks on the > outside of the axes. You can see it here: > > http://matplotlib.sourceforge.net/doc/html/users/pyplot_tutorial.html > > I'm having a terrible time tracking down the cau

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Fernando Perez
On Mon, Jul 7, 2008 at 10:14 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > Yes, but curiously, it doesn't change between those revisions... But it's different from *your* user rc file. That might point to the setting that causes the problem... f -

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Michael Droettboom
Yes, but curiously, it doesn't change between those revisions... Mike Fernando Perez wrote: > On Mon, Jul 7, 2008 at 9:19 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > > >> One other tidbit of information -- the example plots work fine when >> called directly. This only seems to affect

Re: [matplotlib-devel] Example images broken in docs

2008-07-07 Thread Fernando Perez
On Mon, Jul 7, 2008 at 9:19 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > One other tidbit of information -- the example plots work fine when > called directly. This only seems to affect plots generated for the docs. Are the docs built with a custom .matplotlibrc? Maybe there's a differen

[matplotlib-devel] Example images broken in docs

2008-07-07 Thread Michael Droettboom
I noticed today that the examples in the docs have the ticks on the outside of the axes. You can see it here: http://matplotlib.sourceforge.net/doc/html/users/pyplot_tutorial.html I'm having a terrible time tracking down the cause -- maybe I'm just not thinking clearly today. By version bis