The source for the code at
Python HTML
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
mpmath @ 0ce8925
static @ 40d1d80
sympy @ 9a15941 Update SymPy version to 1.0 Apr 28, 2016
.gitmodules Add mpmath submodule Apr 28, 2016
.mailmap Update Alex Houlton's email (at his request) May 25, 2013
LICENSE Update year to 2013 everywhere Jan 20, 2013
TESTING Add a basic document on testing Jan 8, 2013


SymPy Online Shell

Online Shell for SymPy (sympy-live) is a simple web application based on Google App Engine, which allows to evaluate Python code with SymPy in web browsers.

This is accomplished by providing a HTML/JavaScript GUI for entering source code and visualization of output, and a server part which evaluates the requested source code. Note that this shell is not scalable and it uses only one instance on GAE, thus all evaluation requests are queued and it make take quite a lot of time, before our code can be evaluated (depending on the current load of the instance).

Google App Engine has intrinsic 30 second request handling limit, so each evaluation request is a subject to this limit. There are also other limits related to memory consumption, output size, etc. (see Google App Engine documentation for details).


Download and unpack most recent Google App Engine SDK for Python from, e.g.:

$ wget
$ unzip

On the Mac, it is a disk image with an application, which you should drag to your Applications folder. Open the program and install the symlinks (it should ask you the first time you open the application, but if it doesn't, choose "Make Symlinks..." from the GoogleAppEngineLauncher menu). Note that you will have to do this again each time you update the AppEngine program.

Then clone sympy-live repository:

$ git clone git://
$ cd sympy-live

We use submodules to include external libraries in sympy-live:

$ git submodule init
$ git submodule update

This is sufficient to clone appropriate repositories in correct versions into sympy-live (see git documentation on submodules for information).

Development server

Now you are ready to run development web server:

$ ../google_appengine/ .

On the Mac, just run:

$ dev_appserver .

(make sure you installed the symlinks as described above).

I couldn't figure out how to make it work in the GUI (it won't find the sympy git submodule). If you figure out how to do it, please update this file and send a patch describing how to do it.

This is a local server that runs on port 8080 (use --port option to change this). Open a web browser and go to http://localhost:8080. You should see GUI of SymPy Online Shell.

Uploading to GAE

Before updating the the sympy-live app (the official one), you need to do two things. First you need to bump the version in the app.yaml file. Just change the second line ("version") to one more, and commit it (git commit app.yaml -m "Bump version to NN", where NN is the new version) and push it. Second, you need to go to the Versions section of the sympy-live dashboard at and delete the oldest version, as we can only upload ten versions at a time.

Assuming that sympy-live works properly (also across different mainstream web browsers), you can upload your changes to Google App Engine:

$ ../ update .

Or, in Mac OS X, just open the GoogleAppEngineLauncher program, add the project if you haven't already, and click "Deploy" in the toolbar. And then it should just work (follow the log that comes up to see.

This requires admin privileges to If you don't have access to this App Engine application, but want to test it, see the instructions in the Testing on the App Engine section below.

Finally, go to, where NN is the version you just uploaded, and make sure that it works. If it does, go to the Versions section of the sympy-live dashboard, and set this as the new default version. If there are any issues, you can roll back to the previous version from this same screen.

Testing on the App Engine

It's usually a good idea to test big changes on the App Engine itself before deploying, as can only simulate the App Engine. There is a semi-official testing server at If you want write access to it, just ask Aaron Meurer. The convention there is to push to the version corresponding to the pull request (so if you have a branch that is pull request #55, you would push to version 55, and access it by Alternately, you can set up your own testing server (it's free, though it requires a cell phone to set up).

Either way, to test, you will need to edit the app.yaml file. You should edit the first line, application, to the name of the testing application (like sympy-live-tests), and the second line to the version number you want to use.

You should not actually commit these changes to app.yaml, as the official version should still use the sympy-live application. Therefore, it is recommended that you run:

git update-index --assume-unchanged app.yaml

This will make git ignore all changes to the app.yaml file, so that commands like git commit -a will not commit them. This command works on the local level only, so you don't need to worry about it affecting other people who pull your branch.

If you later want to commit an actual change to app.yaml (e.g., to modify some metadata, or to bump the version as described above), you need to run:

git update-index --no-assume-unchanged app.yaml

This will undo the above command, so that git will recognize changes to the file again.

If you have a test app online, remember to update it every time you update a pull request, so that others can easily review your work, without even having to use

Development notes

Make sure SymPy Online Shell works in major mainstream web browsers. This includes Chrome, Firefox, Safari and Internet Explorer. Be extra cautious about trailing commas in JavaScript object and arrays. IE doesn't allow them, so you have to remove them, if any were introduced.

GAE development server allows to use any Python interpreter, but Google App Engine uses Python 2.5, so if the default Python isn't 2.5, then make sure to test your changes to the server part, if it runs properly on 2.5. Also don't use any modules that aren't supported by GAE.

Pulling changes

In projects that don't use submodules, pulling changes boils down to:

$ git pull origin master

in the simplest case. SymPy Live, however, requires additional effort:

$ git submodule update

The above command assures that if there were any changes to submodules of the super-project, then those submodules will get updated to new versions. This is related to the following section.

Updating SymPy

Make sure that you followed instructions above and SymPy's submodule is properly initialized. Assuming that you are in the directory where SymPy Live was cloned, issue:

$ cd sympy/
$ git fetch origin
$ git checkout sympy-0.7.0
$ cd ..
$ git add .
$ git commit -m "Updated SymPy to version 0.7.0"

Now if you issue:

$ git show -v

you should get:

commit 5138e824dc9fd46c243eea2d7c9581a9e58feb08
Author: Mateusz Paprocki <>
Date:   Wed Jul 6 07:45:19 2011 +0200

    Updated SymPy to version 0.7.0

    diff --git a/sympy b/sympy
    index df7a135..c9470ac 160000
    --- a/sympy
    +++ b/sympy
    @@ -1 +1 @@
    -Subproject commit df7a135a4ff7eca361ebbb07ccbeabf8654a8d80
    +Subproject commit c9470ac4f44e7dacfb026cf74529db3ec0822145

This was done for SymPy's version 0.7.0, so in future updates of SymPy replace 0.7.0 with appropriate newer version (e.g. 0.7.1) and you are done (of course particular SHA signatures will be different in your case). If unsure, refer to git help submodule or git book:

Original info

An interactive, stateful AJAX shell that runs Python code on the server.

Part of

May be run as a standalone app or in an existing app as an admin-only handler. Can be used for system administration tasks, as an interactive way to try out APIs, or as a debugging aid during development.

The logging, os, sys, db, and users modules are imported automatically.

Interpreter state is stored in the datastore so that variables, function definitions, and other values in the global and local namespaces can be used across commands.

To use the shell in your app, copy, static/, and templates/ into your app's source directory. Then, copy the URL handlers from app.yaml into your app.yaml.