<div dir="ltr">The issue you pasted led here: <a href="https://github.com/ipython/ipython/issues/1675">https://github.com/ipython/ipython/issues/1675</a><div><br></div><div>Which led to here in the end: <a href="https://github.com/paulgb/runipy">https://github.com/paulgb/runipy</a></div>
<div><br></div><div>I'm not sure if there is an "official" way to do it, but runipy seems like it's worth looking into.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 22, 2013 at 5:46 PM, Anthony Scopatz <span dir="ltr"><<a href="mailto:scopatz@gmail.com" target="_blank">scopatz@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><div class="im">On Tue, Oct 22, 2013 at 7:38 PM, Chris Malone <span dir="ltr"><<a href="mailto:chris.m.malone@gmail.com" target="_blank">chris.m.malone@gmail.com</a>></span> wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">So I also thought there was a way to do this, but it looks like there isn't: <a href="https://github.com/ipython/nbconvert/issues/13" target="_blank">https://github.com/ipython/nbconvert/issues/13</a></div>
</blockquote><div><br></div></div>I agree with pi here. Executing all while saving or converting is a bad idea.</div><div class="gmail_quote"><br></div><div class="gmail_quote">However, a command line interface or a way from python to execute all cells is really useful to have.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">Be Well</div><div class="gmail_quote"><span class="HOEnZb"><font color="#888888">Anthony</font></span><div><div class="h5"><br><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><br></div><div>
The button for it is to evaluate all the cells. Then you would need to save that ipynb, and run nbconvert on the completely evaluated notebook, as I understand.</div><span><font color="#888888"><div><br></div><div>
Chris</div></font></span></div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Oct 22, 2013 at 5:29 PM, Anthony Scopatz <span dir="ltr"><<a href="mailto:scopatz@gmail.com" target="_blank">scopatz@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>On Tue, Oct 22, 2013 at 7:24 PM, Nathan Goldbaum <span dir="ltr"><<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>></span> wrote:<br></div><div class="gmail_extra">
<div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">If we keep the evaluated notebooks in the repo, we need to store the images since they're inlined as strings in the ipynb file.<div>
<br></div><div>I'm not sure if it's possible to programatically evaluate all the cells in a notebook. If we can do that, that's probably the way to go.</div></blockquote><div><br></div></div><div>This has to be possible. There is a button for it =). if not we should complain / issue a PR until it is there.</div>
<div><br></div><div>Be Well</div><span><font color="#888888"><div>Anthony</div></font></span><div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span><font color="#888888">
<div><br></div></font></span><div><span><font color="#888888">Nathan</font></span><div><div><span></span><br><br>On Tuesday, October 22, 2013, Chris Malone wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="auto"><div>
I'm not by any means an expert on this, but can't we do something similar where each commit runs nbconvert on the ipynb to create static HTML and images that are then pushed to the web? I'm not sure I understand the need to actually keep the images within the repo. What am I missing?</div>
<div><br>On Oct 22, 2013, at 4:24 PM, Nathan Goldbaum <<a>nathan12343@gmail.com</a>> wrote:<br><br></div><blockquote type="cite">
<div><div dir="ltr">I know I originally suggested moving to notebooks, but upon further reflection I think it might be too much of a pain for us to manage. Given that the notebooks would be pretty useless if they came down un-evaluated, we would need to store many images in the docs repo.<div>
<br></div><div>I think our current solution of static scripts along with a sphinx plugin that gets executed in a docs build for every commit to the docs repo is a good one.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Oct 22, 2013 at 1:13 PM, Cameron Hummels <span dir="ltr"><<a>chummels@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Hey everyone,<div><br></div><div>The documentation sprint is next Monday and Tuesday for those of you who want to participate. I'll send out another email regarding that in the next day or so.</div><div>
<br></div><div>In preparation for that, though, I wanted to request input from the developer community on something related to the docs.</div><div><br></div><div>Right now, the cookbook page contains a lot of recipes for doing various things, and I think it is hugely beneficial to the community to maintain this (I personally use this page a lot too!). However, with the advent of ipython notebooks over the last year, we are faced with a question: should we move toward incorporating more notebooks into our documentation, and specifically, do you we want to transfer the existing cookbook to a series of notebooks for each task?</div>
<div><br></div><div>Benefits:</div><div>--Portability: users can download an entire notebook for both viewing how it should work as well as being able to execute it locally on their own datasets</div><div>--Illustrative: Interim steps in a cookbook can produce output that can show up inside the notebook, instead of being a single script which generates an image/output at the end (as is the case in the current paradigm)</div>
<div>--Narrative: notebooks provide more space for narrating each step, instead of confining any narrative to comments in the recipe itself</div><div><br></div><div>Disadvantages:</div><div>--Work: it is going to take a decent amount of work to move all of the recipes over from the existing cookbook to individual notebooks</div>
<div>--Bulking of repo: In the current paradigm, images associated with each recipe are generated dynamically on the server by executing each script, thereby minimizing the number of files that need to be tracked by mercurial. By moving to a notebook with images that are embedded in each notebook, we'd potentially increase the footprint of the repository substantially, especially if there were frequent updates of individual recipes.</div>
<div><br></div><div>I also like the yt bootcamp notebooks that Matt put together a year ago. I think they are great for getting new users up to speed on how to use various aspects of the code. Perhaps this notebook could make its way into the beginning of the cookbook for a more streamlined approach to the documentation?</div>
<div><br></div><div>So now is your chance to vote:</div><div><br></div><div>Move cookbook to ipython notebooks? +/- 0-1?</div><div><br></div><div>Move yt bootcamp to cookbook? +/- 0-1?</div><div><br></div><div>Comments? Suggestions?</div>
<span><font color="#888888">
<div><br></div><div>Cameron<br clear="all"><div><br></div>-- <br>Cameron Hummels<div>Postdoctoral Researcher</div><div>Steward Observatory</div><div>University of Arizona</div><div><a href="http://chummels.org" target="_blank">http://chummels.org</a></div>
</div></font></span></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a>yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>yt-dev mailing list</span><br><span><a>yt-dev@lists.spacepope.org</a></span><br>
<span><a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a></span><br></div></blockquote></div></blockquote></div></div></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>