Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-03-02 Thread Alan Isaac
David Huard wrote: > I don't know how far we can disgress from the reST syntax using > those plugins, but it's probably something worth looking at. Digression => maintenance burden. Cheers, Alan Isaac ___ Numpy-discussion mailing list Numpy-discussi

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-03-02 Thread David Huard
To get back to the original subject of the thread, there has been a commit today on the docutils plugins branch that allows folks to write their own parser/writer and somehow include it in docutils, without having to rebuild docutils. In other words, NumPy could define a plugin, and if docutils is

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-27 Thread Alexandre Fayolle
On Sun, Feb 25, 2007 at 06:44:37PM +0200, Jouni K. Seppänen wrote: > "Barry Wark" <[EMAIL PROTECTED]> writes: > > > Yes, I agree. I wasn't coming at so much from the goal of making Pylab > > a Matlab clone (as you point out, that's silly, and misses much of the > > advantage of Python), but rather

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-25 Thread Fernando Perez
Hi, On 2/25/07, Jouni K. Seppänen <[EMAIL PROTECTED]> wrote: > I suppose these things could be addressed quite neatly by IPython. > It could even modify your history similarly to what it currently > does with the %magic commands, so that when you type Feel free to play with implementing this, it

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-25 Thread Jouni K . Seppänen
"Barry Wark" <[EMAIL PROTECTED]> writes: > Yes, I agree. I wasn't coming at so much from the goal of making Pylab > a Matlab clone (as you point out, that's silly, and misses much of the > advantage of Python), but rather from the goal of making interactive > use as efficient as possible. When I f

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-15 Thread Alan G Isaac
On Thu, 15 Feb 2007, Keir Mierle apparently wrote: > * Two different header styles >The distinction between >:Parameters: >and >Examples > These are not two items of the same type. ``:Parameters:`` designates a consolidated field (for describing the documented object)

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-15 Thread Keir Mierle
On 2/15/07, Robert Kern <[EMAIL PROTECTED]> wrote: > On 2/15/07, Keir Mierle <[EMAIL PROTECTED]> wrote: > > On the DocstringStandard page I have also put a completely re-done docstring > > for the 'contour' function from matplotlib. I think it is far more readable > > than the original [3]. JDH and

Re: [Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-15 Thread Robert Kern
On 2/15/07, Keir Mierle <[EMAIL PROTECTED]> wrote: > On the DocstringStandard page I have also put a completely re-done docstring > for the 'contour' function from matplotlib. I think it is far more readable > than the original [3]. JDH and other matplotlibheads, what do you think? > Travis, do you

[Numpy-discussion] Unifying numpy, scipy, and matplotlib docstring formats

2007-02-15 Thread Keir Mierle
I'd like to help the docstring formats of numpy, scipy. and matplotlib converge on a high-quality standard (hence the cross-posting). However, before that can happen all maintainers from all three packages need to agree on a format. In the interest of speeding things along, I've taken the liberty o