Skip to main content

An example of a basic sage package

Project description

This package is designed as a simple SageMath package example to serve as a good practice reference for package developers. We follow python recommendations and adapt them to the SageMath community. You can find more advanced documentation on python package creation on How To Package Your Python Code.

This is still a work in progress. Once this example will have stabilized, the plan is to make a cookie cutter template out of it.


Try the demo on binder

Local install from source

Download the source from the git repository:

$ git clone

Change to the root directory and run:

$ sage -pip install --upgrade --no-index -v .

For convenience this package contains a makefile with this and other often used commands. Should you wish too, you can use the shorthand:

$ make install

Install from PyPI

sage_sample is distributed on PyPI. You can install it with the command:

$ sage -pip install sage_sample

To distribute your own package on PyPI, you will need an account on (maybe at first on

You also need to install setuptools, wheel and twine:

$ sage -pip install –upgrade setuptools wheel twine

Make the package:

$ python sdist bdist_wheel

Upload and test the package to the test PyPI repository:

$ twine upload –repository-url dist/* $ sage -pip install -i sage_sample

And later, upload your distribution to the real PyPI [optionally sign it with GPG]:

$ twine upload [-s] dist/*


Once the package is installed, you can use it in Sage with:

sage: from sage_sample import answer_to_ultimate_question
sage: answer_to_ultimate_question()

See also the demo notebook.


All packaging setup is done through To create your own package follow the strcuture of the file and change the parameters accordingly.

Source code

All source code is stored in the folder sage_sample using the same name as the package. This is not mandatory but highly recommended for clarity. All source folder must contain a file with needed includes.


This package is configured for tests written in the documentation strings, also known as doctests. For examples, see this source file. See also SageMath’s coding conventions and best practices document. With additional configuration, it would be possible to include unit tests as well.

Once the package is installed, one can use the SageMath test system configured in to run the tests:

$ sage test

This is just calling sage -t with appropriate flags.


$ make test


The documentation of the package can be generated using Sage’s Sphinx installation:

$ cd docs
$ sage -sh -c "make html"


$ make doc

For this to work on your own package, make sure you follow the same structure as we do here:

  • Create a docs folder containing the exact same Makefile and a source folder.
  • Copy and paste the docs/source/ file from this package and update the few project specific variables at the beginning of the file.
  • Create an index.rst file as well as a <module name>.rst file for each module you want on the documentation.

Travis CI integration

Scripts that run make test on various SageMath versions on the Travis CI system are included. explains how to enable automatic Travis CI builds for your GitHub-hosted project.

The scripts download and install binary releases (7.1-7.4) from a SageMath mirror. Edit if some optional or experimental SageMath packages need to be installed prior to running your package. Edit .travis.yml to change the list of SageMath versions used.

Automatically deploying documentation to GitHub pages using Travis CI

  • First do the steps described above to enable Travis CI integration of your GitHub-hosted project.

  • If you don’t already have GitHub pages for your project: Create and checkout a branch gh-pages in your repository and put an empty file .nojekyll in it (see Then commit it and push it to GitHub:

    $ git clone --single-branch --depth 1 gh-pages
    $ cd gh-pages
    $ git checkout --orphan gh-pages
    $ git rm -rf .
    $ touch .nojekyll
    $ git add .nojekyll
    $ git commit -m "Initial commit"
    $ git push -u origin gh-pages
    $ cd ..
  • (Back in your working copy:) Generate a new ssh key pair with an empty passphrase:

    $ ssh-keygen -t dsa -f .travis_ci_gh_pages_deploy_key
  • Add the public ssh key (contents of the file to your GitHub repository as a deploy key (Settings/Deploy keys/Add deploy key). Title: Key for deploying documentation to GitHub pages. Check Allow write access.

  • Install the Travis CI command-line client from

    $ gem install travis
  • Log in to Travis CI using your GitHub credentials:

    $ travis login
  • Encrypt the private ssh key, add the decryption keys as secure environment variables to Travis CI, and add code to .travis.yml to decrypt it:

    $ travis encrypt-file .travis_ci_gh_pages_deploy_key --add before_script
  • Add the encrypted private ssh key to the repository:

    $ git add .travis_ci_gh_pages_deploy_key.enc
  • Have git ignore the other keys (and the gh-pages directory):

    $ echo >> .gitignore
    $ echo "/.travis_ci_gh_pages_deploy_key" >> .gitignore
    $ echo "/" >> .gitignore
    $ echo "/gh-pages" >> .gitignore
    $ git add .gitignore
  • Optionally, edit .travis.yml to adjust variables DEPLOY_DOC_...

  • Commit all changes to GitHub. The Travis CI build should then run automatically and deploy it:

    $ git add .travis.yml
    $ git commit -m "Deploy built documentation to GitHub"
    $ git push
  • The deployed documentation will be available at: This can be customized by changing DEPLOY_DOC_TO_DIRECTORY=/ to another directory in .travis.yml For example, setting DEPLOY_DOC_TO_DIRECTORY=doc/html will make the deployed documentation available at:

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for sage-sample, version 0.3.0
Filename, size File type Python version Upload date Hashes
Filename, size sage_sample-0.3.0-py2-none-any.whl (9.0 kB) File type Wheel Python version py2 Upload date Hashes View hashes
Filename, size sage_sample-0.3.0.tar.gz (25.6 kB) File type Source Python version None Upload date Hashes View hashes

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page