A blog post on the ipython notebook: a historical recap and notes about the Sage notebook

163 views
Skip to first unread message

Fernando Perez

unread,
Jan 8, 2012, 7:43:58 PM1/8/12
to IPython Development list, sage-notebook
Hi all,

prompted by a question on the ipython user list about the IPython
notebook and the Sage one, I ended up writing a fairly long blog post
on the matter:

http://blog.fperez.org/2012/01/ipython-notebook-historical.html

It's mainly a history of the IPython notebook, but it tries to also
answer the user's question about where it stands in relation to the
Sage one; I figured some of you might find these notes interesting.

Feedback and corrections welcome, of course!

Cheers,

f

William Stein

unread,
Jan 9, 2012, 1:32:47 AM1/9/12
to sage-n...@googlegroups.com, IPython Development list
The only use of twisted in the version of the notebook we use for sagenb.org and will release in sage 5.0 is via WSGI.  Everything else that used to use twisted now uses flask.  Thus your reason for sagenb being hard to port to python 3 is wrong.  It's surely still hard, but not for that reason.


> Cheers,
>
> f
>

--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

Fernando Perez

unread,
Jan 9, 2012, 1:38:59 AM1/9/12
to sage-n...@googlegroups.com, IPython Development list
On Sun, Jan 8, 2012 at 10:32 PM, William Stein <wst...@gmail.com> wrote:
> The only use of twisted in the version of the notebook we use for sagenb.org
> and will release in sage 5.0 is via WSGI.  Everything else that used to use
> twisted now uses flask.  Thus your reason for sagenb being hard to port to
> python 3 is wrong.  It's surely still hard, but not for that reason.

Ah, ok, that's great to hear. The road for Python3 in Twisted looks
like it will be a slow one, so I'm glad that dependency is gone for
Sage. I'll update that in the post, thanks for the correction.

Cheers,

f

Jason Grout

unread,
Jan 9, 2012, 6:16:52 AM1/9/12
to sage-n...@googlegroups.com


Very nice! I think it might make sense to add in the opening paragraph
to "Other differences with the Sage notebook" that the Sage notebook is
meant to scale to big centralized multi-user servers (sagenb.org, with
about 76,000 accounts, is a good example). That is hinted when you say
it's built on a google docs model, but explicitly saying that draws a
big contrast with the single-user focus from the first sentence.

Thanks,

Jason

Fernando Perez

unread,
Jan 9, 2012, 9:48:04 PM1/9/12
to sage-n...@googlegroups.com
On Mon, Jan 9, 2012 at 3:16 AM, Jason Grout <jason...@creativetrax.com> wrote:
> Very nice!  I think it might make sense to add in the opening paragraph to

Thanks.

> "Other differences with the Sage notebook" that the Sage notebook is meant
> to scale to big centralized multi-user servers (sagenb.org, with about
> 76,000 accounts, is a good example).  That is hinted when you say it's built
> on a google docs model, but explicitly saying that draws a big contrast with
> the single-user focus from the first sentence.

Good point, I just added this using your language.

By all means do let me know of other clarifications/fixes esp.
regarding the Sage nb. I think I have a reasonable understanding of
the development of Sage and did my best to make it justice. But I
have by no means followed it at the level of a developer, so I'm more
than happy to hear feedback.

Cheers,

f

Reply all
Reply to author
Forward
0 new messages