IPython notebook -
http://ipython.org/ipython-doc/dev/interactive/htmlnotebook.htm -
QQQ
A notebook is a combination of two things:
An interactive session connected to an IPython kernel, controlled
by a web application that can send input to the console and display
many types of output (text, graphics, mathematics and more). This is
the same kernel used by the Qt console, but in this case the web
console sends input in persistent cells that you can edit in-place
instead of the vertically scrolling terminal style used by the Qt
console.
A document that can save the inputs and outputs of the session as
well as additional text that accompanies the code but is not meant for
execution. In this way, notebook files serve as a complete
computational record of a session including explanatory text and
mathematics, code and resulting figures. These documents are
internally JSON files and are saved with the .ipynb extension.
QQQ
ipython notebook intro screencast -
http://www.youtube.com/watch?feature=player_detailpage&v=HaS4NXxL5Qc#t=170s
(found by way of http://software-carpentry.org/2012/03/the-ipython-notebook/)
--
-matt
http://pyvideo.org/video/605/ipython-in-depth-high-productivity-interactive-a
BTW pyvideo.org seems to have high quality vids of the entire pycon 2012
and much more.
Thanks,
Kent
> --
> You received this message because you are subscribed to the Google Groups "leo-editor" group.
> To post to this group, send email to leo-e...@googlegroups.com.
> To unsubscribe from this group, send email to leo-editor+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
>
> IPython notebook -
> http://ipython.org/ipython-doc/dev/interactive/htmlnotebook.htm -
Thanks to you and to Kent for the various links. They will be worth
careful study. After b1, that is :-)
EKR
>> IPython notebook -
>> http://ipython.org/ipython-doc/dev/interactive/htmlnotebook.htm -
>
> Thanks to you and to Kent for the various links. They will be worth careful study. After b1, that is :-)
Making the ipython plugin functional again is, by far, the most
important project on the to-do list. In fact, the "keeping up with
ipython" project is likely to pay dividends for a long time.
Edward
Making the ipython plugin functional again is, by far, the most important project on the to-do list. In fact, the "keeping up with
ipython" project is likely to pay dividends for a long time.
> Perhaps the connection is tenuous, but I hope we can keep the inspiration
> engendered by these threads in mind as related aspects of Leo move forward?
Thanks for these comments. It's always good to be reminded of
possible cool features.
Leo's screenshots page now emphasizes the rendering that can already
be done. In the "keeping up with IPython" realm, it would be good to
have viewrendered support MatPlotLib. That would make a good demo.
Feel free to add a wishlist bug ;-)
Bret Victor's video is more of a challenge, but imo the recent work
with weightless/waitless unit testing is related. Also, the
leoInspect module promises substantially faster analysis of python
programs. How (or whether) that promise gets fulfilled is an open
question.
In short, these two recent projects are, in fact, substantial steps
forward, even if they lack the pizazz of Bret's demo.
Edward