Re: [matplotlib-devel] Sphinx custom extension mess, and patches

2009-02-19 Thread Georg Brandl
Michael Droettboom schrieb: > Gael, > > You raise a very good point about the duplication of code around. As a > case in point, the patches you provided no longer apply to the > "canonical" (or at least original) versions of the plugins that began > life in matplotlib. Recent versions of Sphi

Re: [matplotlib-devel] Sphinx custom extension mess, and patches

2009-02-19 Thread Georg Brandl
Gael Varoquaux schrieb: > Hi all, > > Sorry for the multiple posting, this concerns various groups, and I'd > rather the information not be lost. > > While working on getting our in-lab library ready to be merged with NiPy, > I ran into some sort of 'sphinx extension mess' where various sphinx >

Re: [matplotlib-devel] Sphinx custom extension mess, and patches

2009-02-16 Thread Gael Varoquaux
On Tue, Feb 17, 2009 at 12:17:17AM +0100, Georg Brandl wrote: > I'm all for it. In the case of autosummary, I'm guilty of not getting it > in sooner. This will change soon. In other cases, I don't even know of > the extension, probably because those who write it deem it as too > project-specific

Re: [matplotlib-devel] Sphinx custom extension mess, and patches

2009-02-16 Thread Michael Droettboom
Gael, You raise a very good point about the duplication of code around. As a case in point, the patches you provided no longer apply to the "canonical" (or at least original) versions of the plugins that began life in matplotlib. Recent versions of Sphinx have a proper extension API, so that

[matplotlib-devel] Sphinx custom extension mess, and patches

2009-02-15 Thread Gael Varoquaux
Hi all, Sorry for the multiple posting, this concerns various groups, and I'd rather the information not be lost. While working on getting our in-lab library ready to be merged with NiPy, I ran into some sort of 'sphinx extension mess' where various sphinx extension would have side effects on eac