On 2011-12-06, Fernando Perez wrote: > On Thu, Dec 1, 2011 at 9:04 AM, Friedrich Romstedt ><friedrichromst...@gmail.com> wrote: >> 2011/12/1 Fernando Perez <fperez....@gmail.com>: >>> On Thu, Dec 1, 2011 at 2:56 AM, Friedrich Romstedt >>> <friedrichromst...@gmail.com> wrote:
> Many thanks for the informative posts and discussion. It does seem > that sphinx is actually getting closer and closer to what at least we > in ipython will need for solid rest-based latex export of > computational sessions. For converting a single session into a single document, I would recommend Docutils over Sphinx. The additional layer introduced by Sphinx is mainly to accomodate larger projects consisting of a set of documents. > For those who may be curious, there are already users 'publishing' from > ipython notebooks, in the form of blog posts: > http://lighthouseinthesky.blogspot.com/2011/10/curve-fitting-part-5-pymc.html > Unfortunately right now that requires manual cleanup of the html/CSS, > so we'd like to make it more user-friendly. But the real goal in the > long term is to at least narrow the gap between the environment you > work in to obtain your results, and what you write up as a final > paper. There is enough touchup involved in a paper that the final > form will probably always be something edited in TeX/LyX/etc, but > hopefully that will be a document that can be started from a closely > related, and otherwise scientifically equivalent, executable session. > Then you could supply, as part of your supplementary materials, this > notebook. There are obviously issues with how to expose your data, > etc, that are non-trivial and the subject of much current discussion > at journal editorial boards, funding agencies and research centers, > but at least I think this can be a contribution in the right > direction. Advertisement: For the related topic of a non-interactive scripts: I recommend a look at PyLit (Python Literate) provides a plain but efficient tool for literate programming: a bidirectional text/code converter. -- http://pylit.berlios.de/ With this, a program source can be easily converted between “text” and “code” formats The “code” source can be debugged, compiled or executed with standard tools. The “text” source can be converted to HTML or LaTeX documents, e.g. with the Docutils or Sphinx. Both formats hold the full information. Round-trips are possible without loss, hence it is easy to keep them up-to-date during development. Günter -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
