Sage Notebook Development

Home

How to do development

Get the Sage Notebook source code. The sagenb package (sagenb-x.y.z.spkg) is included in the spkg/standard subdirectory of the Sage source tarball. It can also be downloaded from the Sage standard package repository. More bleeding edge versions of the sagenb package may be available here.
Extract the source package and develop as usual:
```
$ tar -xvf sagenb-x.y.z.spkg
$ cd sagenb-x.y.z/src/sagenb/
$ python setup.py install && python setup.py develop
```
NOTE: If you're developing in Sage, be sure to type sage -python instead of python above. The command setup.py develop above allows you to develop on the package without needing to reinstall the package (via python setup.py install).
Make patches To make a patch, type:
```
hg commit
hg export tip  > test.patch
```
Read more about Mercurial (the hg command), and consider using Mercurial queues, which make Mercurial much more pleasant to use.
Submit your code Use the Sage trac server, which you can quickly get an account on, and read about the Sage development process (ignore stuff about cloning).

There is a source code repository where you can browse the history of the notebook. You can also pull the latest development version of the code:

   hg pull http://boxen.math.washington.edu:8123
   hg update

There is a brief technical overview of how the Sage notebook works.
Consult Twisted's howto and wiki (specifically, web2, despite it being described as "now defunct").
The Codenode project is a good source of ideas and source code. Their license is BSD, so one can take anything from the codenode codebase and add it to the Sage notebook.