Hello all, I did some work in converting the Cookbook to Sphinx: I scraped the Cookbook from the archive Robert sent to the list earlier and used a couple of scripts to make the conversion, it's not perfect but not that bad either. You can see the results at: http://mpastell.github.io/ I put the various stages of conversion to GitHub with a brief explanation: https://github.com/mpastell/SciPy-CookBook Conversion scripts currently require a forked version of Pweave http://mpastell.com/pweave (I'm the author) that only I have, but of course I can share it. I'd like to get some feedback before I do any more work and I think a lot of the pages will require a bit of manual editing in the end. Also what do you think about using Pweave for the Cookbook? It can be used to capture figures and code and can be intgrated to sphinx build process. An example (http://mpastell.com/pweave/examples.html). Matti
Hi, I've added a conversion to IPython notebook script format (http://ipython.org/ipython-doc/stable/interactive/htmlnotebook.html) in ipython folder in my repository(https://github.com/mpastell/SciPy-CookBook). The script files can be imported to IPython notebook http://ipython.org/ipython-doc/stable/interactive/htmlnotebook.html#exportin.... Let me know what you think, it would be nice to know what format will used for the Cookbook in the future before doing any more work. Best, Matti On 16.5.2013 11:13, Matti Pastell wrote:
Hello all, I did some work in converting the Cookbook to Sphinx: I scraped the Cookbook from the archive Robert sent to the list earlier and used a couple of scripts to make the conversion, it's not perfect but not that bad either.
You can see the results at: http://mpastell.github.io/
I put the various stages of conversion to GitHub with a brief explanation: https://github.com/mpastell/SciPy-CookBook
Conversion scripts currently require a forked version of Pweave http://mpastell.com/pweave (I'm the author) that only I have, but of course I can share it.
I'd like to get some feedback before I do any more work and I think a lot of the pages will require a bit of manual editing in the end.
Also what do you think about using Pweave for the Cookbook? It can be used to capture figures and code and can be intgrated to sphinx build process. An example (http://mpastell.com/pweave/examples.html).
Matti
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
-- Matti Pastell, Dr. Agric. & For. University lecturer, Livestock technology Department of Agricultural Sciences P.O Box 28, FI-00014 University of Helsinki, Finland Tel. +358504150612 http://mpastell.com
On Fri, May 17, 2013 at 9:05 AM, Matti Pastell <matti.pastell@helsinki.fi>wrote:
Hi, I've added a conversion to IPython notebook script format (http://ipython.org/ipython-doc/stable/interactive/htmlnotebook.html) in ipython folder in my repository(https://github.com/mpastell/SciPy-CookBook).
The script files can be imported to IPython notebook
http://ipython.org/ipython-doc/stable/interactive/htmlnotebook.html#exportin... .
Let me know what you think, it would be nice to know what format will used for the Cookbook in the future before doing any more work.
Hi Matti, first of all sorry for the slow reply. Looks like you put in quite a bit of work, and the result looks pretty good to me. There are some issues with crosslinks and attachments, but overall the conversion seems to work well. Visually this looks better than the current cookbook imho. And it will definitely be more maintainable. I had heard of Pweave before but hadn't looked at it until just now. The .Pnw format is easily readable and the documentation looks good, so I'm fine with using it. Question I have is how good the automatic conversion to/from IPython notebooks is. Right now you have both in your repo, but keeping both is probably only feasible if conversion is seamless. Long-term we were thinking about migrating the Cookbook content to SciPy Central, but the new and shiny version of that site is not yet ready. Surya is thinking about adding notebook support; adding Pweave support may not be that much more work (not sure about that though). So even if we migrate to SPC later, the work in converting to Pweave/notebooks now is useful. And it will allow us to completely get rid of moinmoin. Cheers, Ralf
Best, Matti
On 16.5.2013 11:13, Matti Pastell wrote:
Hello all, I did some work in converting the Cookbook to Sphinx: I scraped the Cookbook from the archive Robert sent to the list earlier and used a couple of scripts to make the conversion, it's not perfect but not that bad either.
You can see the results at: http://mpastell.github.io/
I put the various stages of conversion to GitHub with a brief
explanation:
https://github.com/mpastell/SciPy-CookBook
Conversion scripts currently require a forked version of Pweave http://mpastell.com/pweave (I'm the author) that only I have, but of course I can share it.
I'd like to get some feedback before I do any more work and I think a lot of the pages will require a bit of manual editing in the end.
Also what do you think about using Pweave for the Cookbook? It can be used to capture figures and code and can be intgrated to sphinx build process. An example (http://mpastell.com/pweave/examples.html).
Matti
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
-- Matti Pastell, Dr. Agric. & For. University lecturer, Livestock technology Department of Agricultural Sciences P.O Box 28, FI-00014 University of Helsinki, Finland Tel. +358504150612 http://mpastell.com _______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
participants (2)
-
Matti Pastell -
Ralf Gommers