nick.bollweg at gmail.com
Thu Oct 23 21:31:51 EDT 2014
Is it worth considering something that works with the existing sphinx
This is used, for example, by safari books online:
And while "jupyter != ipython" might be valid here, the fact remains that
sphinx makes very nice output documents... nice enough to be used by the
official julia documentation, for example!
On Thu, Oct 23, 2014 at 4:04 PM, Jonathan Frederic <jon.freder at gmail.com>
> As a follow up of today's meeting, it looks like, if we don't mind the
> comment appearing before the function, JSDoc allows for our own doc string
> format (see simplest case): http://usejsdoc.org/about-getting-started.html
> . JSDoc claims to be "highly extensible" and has a markdown plugin
> distributed with it. Here's a good article comparing the 4 most popular JS
> comment -> API doc tools:
> My preference is for JSDoc, but I'd like to hear what others think. Also
> the option to NOT use a comment -> doc parser still exists. Provided we
> can commit to keeping a separate API docs by hand.
> IPython-dev mailing list
> IPython-dev at scipy.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev