passagemath: General purpose mathematical software system, a fork of SageMath

passagemath is open source mathematical software in Python, released under the GNU General Public Licence GPLv2+.

It is a fork of SageMath, which has been developed 2005-2025 under the motto "Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, and MATLAB".

The passagemath fork uses the motto "Creating a Free Passage Between the Scientific Python Ecosystem and Mathematical Software Communities." It was created in October 2024 with the following goals:

• providing modularized installation with pip
  • this major project was started in May 2020 in the Sage codebase and completed in passagemath 10.5.29 (May 2025),
• establishing first-class membership in the scientific Python ecosystem,
• giving clear attribution of upstream projects,
• providing independently usable Python interfaces to upstream libraries,
• offering platform portability and integration testing services to upstream projects,
• inviting collaborations with upstream projects,
• building a professional, respectful, inclusive community,
• empowering Sage users to participate in the scientific Python ecosystem by publishing packages,
• developing a port to Pyodide (WebAssembly) for serverless deployment with Javascript,
• developing a native Windows port
  • passagemath 10.6.1 (July 2025) published the first pip-installable packages for native Windows on x86_64.

Full documentation is available online.

passagemath community

Join passagemath.discourse.group for help and discussions.

Join the BlueSky platform and follow @passagemath.org to receive announcements.

As of 2025-08-20, the passagemath GitHub organization had 120 members.

People all around the globe have contributed to the development of SageMath since 2005, and hence of passagemath.

See CONTRIBUTING.md for how you can contribute.

passagemath is a major integrating force in the mathematical software landscape.

Supported Platforms

passagemath attempts to support and provides binary wheels suitable for all major Linux distributions and recent versions of macOS. Binary wheels for native Windows (x86_64) are gradually made available in the passagemath 10.6.x series. Use of the full functionality on Windows currently requires the use of Windows Subsystem for Linux (WSL) or virtualization.

| Version | CPython | Toolchains | Operating Systems | Architectures | Notes | |------------------------------------------------------------------------------|-----------|-------------------|-------------------|---------------|-------------| | 10.4.x | 3.9-3.12 | GCC 8.4-14, clang | Linux, macOS, WSL | x8664, ARM | EOL 2024-12 | | 10.5.x | 3.9-3.13 | GCC 9-14, clang | Linux, macOS, WSL | x8664, ARM | oldstable | | 10.6.x (main) | 3.10-3.13 | GCC 9-15, clang | Linux, macOS, WSL | x8664, ARM | stable | | | | mingw32 + MSVC | Windows (partial) | x8664 | | | 10.7.x (#1051) | 3.11-3.14 | | | | planned |

Detailed information on supported platforms for a specific version of passagemath can be found in the release notes.

Full installation of passagemath from binary wheels on PyPI

Complete sets of binary wheels are provided on PyPI for the supported Python versions for Linux and macOS, both for the x86_64 and ARM architectures.

Unless you need to install passagemath into a specific existing environment, we recommend to create and activate a fresh virtual environment over a supported Python for example ~/passagemath-venv/:

bash session $ python3 --version Python 3.12.7 $ python3 -m venv ~/passagemath-venv $ source ~/passagemath-venv/bin/activate $ rehash

Then install the meta-package

bash session (passagemath-venv) $ pip install -v --prefer-binary passagemath-standard

Start the Sage REPL:

bash session (passagemath-venv) $ sage

Alternatively, use a Python or IPython REPL, or use the Python kernel or the provided Sage kernel in Jupyter.

Modularized distributions

As the installation using pip shows, passagemath provides the Sage library in a large number of distributions (pip-installable packages) that can also be installed separately.

Authors of packages that depend on the Sage library can declare dependencies on these distributions. The benefit for users of the package: There is no longer a need to first install Sage. Instead, the parts of the Sage library that are needed by the package are automatically installed. Thus, the package becomes a first-class member of the Python ecosystem.

• sage-numerical-interactive-mip is an example of a pure Python package that declares dependencies on four distributions: passagemath-polyhedra, passagemath-plot, passagemath-repl, and passagemath-flint.

• kerrgeodesic_gw is an example of a pure Python package that declares optional dependencies ("extras-require") on three distributions: passagemath-symbolics, passagemath-plot, and passagemath-repl.

• See https://github.com/passagemath/passagemath/issues/248 for many more examples how to change a user package to make it ready for passagemath and the Python ecosystem.

Here is an overview of the distribution packages of passagemath.

Distributions named after a basic mathematical structure

The packages may also cover a wide range of generalizations/applications of the structure after which they are named. Users who work in a specialized research area will, of course, recognize what structures they need. The down-to-earth naming also creates discoverability by a broader audience.

provides "everything combinatorial", except for graphs. It consists of about 350 first-party Python and Cython modules and also provides the functionality of SYMMETRICA, the library for representation theory of the symmetric group, combinatorics of tableaux, symmetric functions, etc. (Available on Windows.)

provides directed and undirected graphs, but also posets, combinatorial designs, abstract simplicial complexes, quivers, etc. It consists of over 170 first-party Python and Cython modules and uses the Boost Graph Library, with additional functionality from NetworkX and several other libraries. (Available on Windows.)

provides groups and invariant theory. It heavily depends on GAP via passagemath-gap.

provides vector spaces, modules, matrices, tensors, homology, coding theory, abelian groups, matroids, etc. It consists of over 440 first-party Python and Cython modules and depends on the GNU Scientific Library and NumPy. (Available on Windows.)

provides convex polyhedra in arbitrary dimension on the basis of the Parma Polyhedra Library. It consists of about 130 first-party Python and Cython modules that also provide fans, hyperplane arrangements, polyhedral complexes, linear and mixed-integer optimization, lattice point sets, and toric varieties.

provides algebraic varieties, schemes, elliptic curves, modular forms, etc.

provides symbolic expressions implemented in Pynac, a fork of GiNaC, symbolic calculus using Maxima, and interfaces to various other symbolic software systems including SymPy, as well as differential geometry (SageManifolds).

Distributions named after a third-party non-Python dependency

This makes technical sense because the dependencies will be localized to this distribution package, but it also helps give attribution and visibility to these libraries and projects that Sage depends on. | Standard packages | Optional packages | | :---------------- | :---------------- | | provides the functionality of cddlib, the library for polyhedral representation conversion. (Available on Windows.) | provides the functionality of benzene, generating nonisomorphic fusene and benzenoid graphs. | | provides the functionality of cliquer, finding cliques in weighted graphs. (Available on Windows.) | provides the functionality of bliss, a tool for computing automorphism groups and canonical forms of graphs. | | provides modules depending on eclib, the library for enumerating and computing with elliptic curves defined over the rational numbers. | provides the functionality of BRiAl, a Boolean Ring Algebra implementation using binary decision diagrams (successor to PolyBoRi). | | provides modules depending on FLINT, the Fast Library for Number Theory. | provides the functionality of buckygen, generating nonisomorphic fullerene graphs. | | provides modules depending on GAP, the system for computational discrete algebra with emphasis on Computational Group Theory. | provides the functionality of the Combinatorial Matrix Recognition library, Seymour decomposition of TU matrices etc. (Available on Windows.) | | | provides a mixed-integer linear programming backend using COIN-OR Cbc. | | provides the functionality of gfan, computing Groebner fans and tropical varieties. | provides the functionality of the coxeter3 library. | | | provides a mixed-integer linear programming backend using CPLEX. | | provides the functionality of Giac, a general purpose computer algebra system. | provides the functionality of Frobby, computations on monomial ideals. | | provides a mixed integer linear optimization backend using GLPK, the GNU Linear Programming Kit. (Available on Windows.) | provides an interface to the SAT solver glucose. | | | provides a mixed-integer linear programming backend using Gurobi. | | provides the functionality of libhomfly, the library to compute the homfly polynomial of knots and links. (Available on Windows.) | provides an interface to the SAT solver kissat. | | provides the functionality of lcalc, the L-function calculator. | provides interfaces to LattE integrale and 4ti2 | | provides the functionality of libbraiding, computing centralizers, conjugacy, and other properties of braids. | provides the functionality of lrslib, reverse search for vertex enumeration and convex hull problems. | | provides the functionality of GMP-ECM, the elliptic curve method for integer factorization. | provides an interface to Macaulay2, for computing in commutative algebra, algebraic geometry and related fields. | | provides the functionality of the LinBox suite (Givaro, fflas-ffpack, LinBox) and the libraries IML, m4ri, m4rie. | provides the functionality of mcqd, finding a maximum clique in a graph. | | provides the functionality of nauty and traces, computing automorphism groups of graphs and digraphs. | provides matrices over small finite fields using meataxe. | | provides the functionality of NTL, a library for doing number theory. | provides an interface to msolve, the polynomial system solver. | | provides the functionality of PALP, lattice polytopes with applications to toric geometry. | provides the functionality of plantri, generating planar graphs. | | provides the functionality of PARI/GP, the computer algebra system for fast computations in number theory. | provides the functionality of QEPCAD, quantifier elimination by partial cylindrical algebraic decomposition. | | provides the functionality of the Edge Addition Planarity Suite for graphs. (Available on Windows.) | provides algorithms for Rubik's cube. | | provides the functionality of the Parma Polyhedra Library. | | | provides the functionality of the primesieve and primecount libraries. | | | provides the functionality of rw, rank decompositions of graphs. (Available on Windows.) | provides the functinality of sirocco, certified root continuation of bivariate polynomials. | | provides the functionality from Singular, the CAS for polynomial computations, algebraic geometry, singularity theory. | provides the functionality of treedec, algorithms concerning tree decompositions of graphs. | | provides the functionality of sympow, special values of symmetric power elliptic curve L-functions. | provides the functionality of TOPCOM, triangulations of point configurations and oriented matroids. | | provides the functionality of the ray tracing system tachyon. |

Distributions named after a technical functionality

Sage extends Python's object system by dynamic mix-in classes that are driven by categories and axioms. It is loosely modeled on concepts of category theory and inspired by Scratchpad/Axiom/FriCAS, Magma, and MuPAD. This distribution package makes Sage objects, the element/parent framework, basic categories and functors, the coercion system and the related metaclasses available. It only depends on the basic arithmetic libraries GMP, MPFR, MPC, on the Cython interface gmpy2 to these libraries, and on cysignals. (Available on Windows.)

This distribution package contains the full set of categories defined by Sage, as well as basic mathematical objects such as integers and rational numbers, a basic implementation of polynomials, and affine spaces. None of this brings in additional dependencies. (Available on Windows.)

provides the sage script for launching the Sage REPL and accessing various developer tools and Python modules that provide the connection to the system and software environment. (Available on Windows.)

The top-level interactive environment with the preparser that defines the surface language of Sage. This distribution also includes the doctesting facilities (sage -t), as the doctests are written in the surface language. (Available on Windows.)

Plotting facilities, depending on matplotlib for 2D graphics, three.js for 3D graphics. (Available on Windows.)

Ideally an empty meta-package that depends on everything that is not in passagemath-symbolics; as a catch-all mechanism, this distribution ships all modules that do not carry a # sage_setup: distribution = ... directive.

Everything as provided by a standard installation of the Sage distribution. This is reduced to an empty meta-package.

Confectionery and configuration system.

Build system for the Sage library. (Available on Windows.)

Build system for the Sage documentation.

Building from Source: Table of Contents

The remainder of this README contains self-contained instructions for building passagemath from source. This requires you to clone the git repository (as described in this README).

• [Windows] Preparing the Platform
• [macOS] Preparing the Platform
• Preparation for Building from Source
• Full Installation from Source as passagemath
• Traditional Installation from Source as Sage-the-Distribution
• Use With an Existing Jupyter Installation
• Directory Layout

[Windows] Preparing the Platform

The preferred way to run Sage on Windows is using Windows Subsystem for Linux (WSL). Follow the official WSL setup guide to install Ubuntu (or another Linux distribution). Make sure you allocate WSL sufficient RAM; 5GB is known to work, while 2GB might be not enough for building Sage from source. Then all instructions for installation in Linux apply.

As an alternative, you can also run Linux on Windows using Docker or other virtualization solutions.

[macOS] Preparing the Platform

• If your Mac uses the Apple Silicon (M1, M2, M3, M4; arm64) architecture and you set up your Mac by transferring files from an older Mac, make sure that the directory /usr/local does not contain an old copy of Homebrew (or other software) for the x86_64 architecture that you may have copied over. Note that Homebrew for Apple Silicon is installed in /opt/homebrew, not /usr/local.

• We strongly recommend to use Homebrew ("the missing package manager for macOS") from https://brew.sh/, which provides the gfortran compiler and many libraries.

• Otherwise, if you do not wish to install Homebrew, you will need to install the latest version of Xcode Command Line Tools. Open a terminal window and run xcode-select --install; then click "Install" in the pop-up window. If the Xcode Command Line Tools are already installed, you may want to check if they need to be updated by typing softwareupdate -l.

Preparation for Building from Source

The instructions cover all of Linux, macOS, and WSL.

More details, providing a background for these instructions, can be found in the section Install from Source Code in the Installation Guide.

1. Decide on the source/build directory (SAGE_ROOT):

- Any subdirectory of your :envvar:`HOME` directory should do.

- For example, you could use `SAGE_ROOT=~/sage/passagemath`, which we
  will use as the running example below.

- You need at least 10 GB of free disk space.

- The full path to the source directory must contain **no spaces**.

- After starting the build, you cannot move the source/build
  directory without breaking things.

- You may want to avoid slow filesystems such as
  [network file systems (NFS)](https://en.wikipedia.org/wiki/Network_File_System)
  and the like.

- [macOS] macOS allows changing directories without using exact capitalization.
  Beware of this convenience when compiling for macOS. Ignoring exact
  capitalization when changing into :envvar:`SAGE_ROOT` can lead to build
  errors for dependencies requiring exact capitalization in path names.

1. Clone the sources with git:

- To check that `git` is available, open a terminal and enter
  the following command at the shell prompt (`$`):

        $ git --version
        git version 2.42.0

  The exact version does not matter, but if this command gives an error,
  install `git` using your package manager, using one of these commands:

        $ sudo pacman -S git                          # on Arch Linux
        $ sudo apt-get update && apt-get install git  # on Debian/Ubuntu
        $ sudo yum install git                        # on Fedora/Redhat/CentOS
        $ sudo zypper install git                     # on openSUSE
        $ sudo xbps-install git                       # on Void Linux

- Create the directory where `SAGE_ROOT` should be established:

        $ mkdir -p ~/sage
        $ cd ~/sage

- Clone the passagemath git repository:

        $ git clone -c core.symlinks=true --filter blob:none  \
                    --origin passagemath \
                    https://github.com/passagemath/passagemath.git

  This will create the subdirectory `~/sage/passagemath`. (See the section
  [Setting up git](https://passagemath.org/docs/latest/html/en/developer/git_setup.html)
  and the following sections in the Sage Developer's Guide
  for more information.)

- Change into the created subdirectory:

        $ cd passagemath

- [Windows] The passagemath source tree contains symbolic links, and the
  build will not work if Windows line endings rather than UNIX
  line endings are used.

  Therefore it is recommended (but not necessary) to use the
  WSL version of `git`.

1. Install system packages.

   Either refer for this to the section on installation from source in the Sage Installation Manual for compilations of system packages that you can install.

   The precise list of packages varies with the version of your distribution. If a package is not available and gives an error, just skip it and try again with the rest of the packages.

   When done, skip to step 7 (bootstrapping).

   Alternatively, follow the more fine-grained approach below.

2. [Linux, WSL] Install the required minimal build prerequisites:

- Compilers: `gcc`, `gfortran`, `g++` (GCC versions from 9.x to 14.x
  and recent versions of Clang (LLVM) are supported).
  See [build/pkgs/gcc/SPKG.rst](build/pkgs/gcc/SPKG.rst) and
  [build/pkgs/gfortran/SPKG.rst](build/pkgs/gfortran/SPKG.rst)
  for a discussion of suitable compilers.

- Build tools: GNU `make`, GNU `m4`, `perl` (including
  `ExtUtils::MakeMaker`), `ranlib`, `git`, `tar`, `bc`.
  See [build/pkgs/_prereq/SPKG.rst](build/pkgs/_prereq/SPKG.rst) for
  more details.

- Python 3.4 or later, or Python 2.7, a full installation including
  `urllib`; but ideally version 3.10.x or later, which
  will avoid having to build Sage's own copy of Python 3.
  See [build/pkgs/python3/SPKG.rst](build/pkgs/python3/SPKG.rst)
  for more details.

We have collected lists of system packages that provide these build
prerequisites. See, in the folder
[build/pkgs/_prereq/distros](build/pkgs/_prereq/distros),
the files
[arch.txt](build/pkgs/_prereq/distros/arch.txt),
[debian.txt](build/pkgs/_prereq/distros/debian.txt)
(also for Ubuntu, Linux Mint, etc.),
[fedora.txt](build/pkgs/_prereq/distros/fedora.txt)
(also for Red Hat, CentOS),
[opensuse.txt](build/pkgs/_prereq/distros/opensuse.txt),
[slackware.txt](build/pkgs/_prereq/distros/slackware.txt), and
[void.txt](build/pkgs/_prereq/distros/void.txt), or visit
https://passagemath.org/docs/latest/html/en/reference/spkg/_prereq.html#spkg-prereq

1. Optional: It is recommended that you have both LaTeX and the ImageMagick tools (e.g. the "convert" command) installed since some plotting functionality benefits from them.

2. Install the bootstrapping prerequisites. See the files in the folder build/pkgs/_bootstrap/distros, or visit https://passagemath.org/docs/latest/html/en/reference/spkg/_bootstrap.html#spkg-bootstrap

3. Sanitize the build environment. Use the command

   $ env
   

   to inspect the current environment variables, in particular PATH, PKG_CONFIG_PATH, LD_LIBRARY_PATH, CFLAGS, CPPFLAGS, CXXFLAGS, and LDFLAGS (if set).

   Remove items from these (colon-separated) environment variables that Sage should not use for its own build. In particular, remove items if they refer to a previous Sage installation.

- [WSL] In particular, WSL imports many items from the Windows
  `PATH` variable into the Linux environment, which can lead to
  confusing build errors. These items typically start with `/mnt/c`.
  It is best to remove all of them from the environment variables.
  For example, you can set `PATH` using the command:

        $ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/wsl/lib

- [macOS with homebrew] Set required environment variables for the build:

        $ source ./.homebrew-build-env

  This is to make some of Homebrew's packages (so-called keg-only
  packages) available for the build. Run it once to apply the
  suggestions for the current terminal session. You may need to
  repeat this command before you rebuild Sage from a new terminal
  session, or after installing additional homebrew packages.  (You
  can also add it to your shell profile so that it gets run
  automatically in all future sessions.)

1. Bootstrap the source tree using the following command:

   $ make configure
   

Full Installation from Source as passagemath

1. Unless you need to install passagemath into a specific existing environment, we recommend to create and activate a fresh virtual environment over a suitable Python (3.10.x-3.13.x), for example ~/passagemath-venv/ as follows. (Dollar signs are prompts; do not type them.)

   bash session $ python3 --version Python 3.12.7 $ python3 -m venv ~/passagemath-venv $ source ~/passagemath-venv/bin/activate $ rehash

2. Let's configure it so that all passagemath-* packages are built from your local clone of the passagemath repository.

   bash session (passagemath-venv) $ export SAGE_ROOT=$(pwd) (passagemath-venv) $ export PIP_CONSTRAINT="$(pwd)/constraints_pkgs.txt" (passagemath-venv) $ export SAGE_CONF_TARGETS="build-local"

   If you wish to build all Python dependencies from source as well, using the pinned and patched versions defined by the Sage distribution, instead of taking them from binary wheels on PyPI, replace the last command by:

   bash session (passagemath-venv) $ export SAGE_CONF_TARGETS="build"

3. Now install , which builds various all prerequisite non-Python packages in a subdirectory of ~/.sage/, as well as the requested wheels.

   The build can be customized by setting SAGE_CONF_CONFIGURE_ARGS.

   bash session (passagemath-venv) $ python3 -m pip cache remove passagemath_conf (passagemath-venv) $ python3 -m pip install --force-reinstall -v passagemath-conf

4. Depending on what you chose above, a wheelhouse may now provide various Python packages. You can list the wheels using the command:

   bash session (passagemath-venv) $ ls $(sage-config SAGE_SPKG_WHEELS)

   If this gives an error saying that sage-config is not found, check any messages that the pip install command may have printed. You may need to adjust your PATH, for example by:

   bash session (passagemath-venv) $ export PATH="$(python3 -c 'import sysconfig; print(sysconfig.get_path("scripts", "posix_user"))'):$PATH" (passagemath-venv) $ ls $(sage-config SAGE_SPKG_WHEELS)

5. If there are any wheels, arrange for them to be picked up from the wheelhouse:

   bash session (passagemath-venv) $ export PIP_FIND_LINKS=$(sage-config SAGE_SPKG_WHEELS) (passagemath-venv) $ export PIP_PREFER_BINARY=1

6. Finally, install the Sage library into your virtual environment using the meta-package :

   bash session (passagemath-venv) $ python3 -m pip install -v passagemath-standard

7. Type sage to try it out. At the Sage prompt, try for example 2 + 2, plot(x^2), plot3d(lambda x, y: x*y, (-1, 1), (-1, 1)) to test a simple computation and plotting in 2D and 3D. Type Ctrl+D or quit to quit Sage.

Traditional Installation from Source as Sage-the-Distribution

1. Optionally, decide on the installation prefix (SAGE_LOCAL):

- Traditionally, and by default, Sage is installed into the
  subdirectory hierarchy rooted at `SAGE_ROOT/local/`.

- This can be changed using `./configure --prefix=SAGE_LOCAL`,
  where `SAGE_LOCAL` is the desired installation prefix, which
  must be writable by the user.

  Unless you use this option in combination with `--enable-editable`,
  you can delete the entire Sage source tree after completing
  the build process.  What is installed in `SAGE_LOCAL` will be
  a self-contained installation of Sage.

- Note that in Sage's build process, `make` builds **and**
  installs (`make install` is a no-op).  Therefore the
  installation hierarchy must be writable by the user.

- See the Sage Installation Manual for options if you want to
  install into shared locations such as `/usr/local/`.
  Do not attempt to build Sage as `root`.

1. Optionally, review the configuration options, which includes many optional packages:

   $ ./configure --help
   

   Notable options for Sage developers are the following:

- Use the option `--config-cache` to have `configure`
  keep a disk cache of configuration values. This gives a nice speedup
  when trying out ticket branches that make package upgrades, which
  involves automatic re-runs of the configuration step.

- Use the option `--enable-ccache` to have Sage install and use the
  optional package `ccache`, which is preconfigured to keep a
  disk cache of object files created from source files. This can give
  a great speedup when switching between different branches, at the
  expense of disk space use.

1. Optional, but highly recommended: Set some environment variables to customize the build.

   The MAKEFLAGS variable controls whether to run several jobs in parallel. To saturate all the execution threads of your CPU, we recommend to run export MAKEFLAGS="-j$(nproc) -l$(nproc).5" if you are on Linux, and export MAKEFLAGS="-j$(sysctl -n hw.ncpu) -l$(sysctl -n hw.ncpu).5" if you are on macOS.

   Note that the compilation may nonetheless use a different number of processes, e.g., for parts that are built with ninja which automatically decides on the amount of parallelity to use. In practice, you might therefore see twice as many processes during the build process than your CPU has execution threads. Unless your system is low on RAM, this should not affect the time the compilation takes substantially.

   To reduce the terminal output during the build, type export V=0. (V stands for "verbosity".)

   Some environment variables deserve a special mention: CC, CXX and FC. These variables defining your compilers can be set at configuration time and their values will be recorded for further use at build time and runtime.

   For an in-depth discussion of more environment variables for building Sage, see the installation guide.

2. Type ./configure, followed by any options that you wish to use. For example, to build Sage with gf2x package supplied by Sage, use ./configure --with-system-gf2x=no.

   At the end of a successful ./configure run, you may see messages recommending to install extra system packages using your package manager.

   For a large list of Sage packages, Sage is able to detect whether an installed system package is suitable for use with Sage; in that case, Sage will not build another copy from source.

   Sometimes, the messages will recommend to install packages that are already installed on your system. See the earlier configure messages or the file config.log for explanation. Also, the messages may recommend to install packages that are actually not available; only the most recent releases of your distribution will have all of these recommended packages.

3. Optional: If you choose to install the additional system packages, a re-run of ./configure will test whether the versions installed are usable for Sage; if they are, this will reduce the compilation time and disk space needed by Sage. The usage of packages may be adjusted by ./configure parameters (check again the output of ./configure --help).

4. Type make build. That's it! Everything is automatic and non-interactive.

   If you followed the above instructions, in particular regarding the installation of system packages recommended by the output of ./configure (step 10), and regarding the parallel build (step 11), building Sage takes less than one hour on a modern computer. (Otherwise, it can take much longer.)

   The build should work fine on all fully supported platforms. If it does not, we want to know!

5. Type ./sage to try it out. In Sage, try for example 2 + 2, plot(x^2), plot3d(lambda x, y: x*y, (-1, 1), (-1, 1)) to test a simple computation and plotting in 2D and 3D. Type Ctrl+D or quit to quit Sage.

6. Optional: Type make ptestlong to test all examples in the documentation (over 200,000 lines of input!) -- this takes from 10 minutes to several hours. Don't get too disturbed if there are 2 to 3 failures, but always feel free to email the section of logs/ptestlong.log that contains errors to the sage-support mailing list. If there are numerous failures, there was a serious problem with your build.

7. Optional: If you want to build a local HTML version of the documentation, run make doc-html. After a successful build, it resides in the directory local/share/doc/sage/html/. You may want to bookmark it in your browser.

8. Optional: If you want to build the PDF version of the documentation, run make doc-pdf (this requires LaTeX to be installed).

9. Optional: Install optional packages of interest to you: get a list by typing ./sage --optional or by visiting the packages documentation page.

10. Optional: Create a symlink to the installed sage script in a directory in your PATH, for example /usr/local/bin/. This will allow you to start Sage by typing sage from anywhere rather than having to either type the full path or navigate to the Sage directory and type ./sage. This can be done by running:

    $ sudo ln -s $(./sage -sh -c 'ls $SAGE_ROOT/venv/bin/sage') /usr/local/bin
    

Use With an Existing Jupyter Installation

1. Optional: Set up SageMath as a Jupyter kernel in an existing Jupyter notebook or JupyterLab installation, as described in the section Launching SageMath in the Sage Installation Guide.

Directory Layout

Simplified directory layout: SAGE_ROOT Root directory (create by git clone) COPYING.txt Copyright information pkgs Source trees of Python distribution packages sage-conf sage_conf.py setup.py sage-docbuild sage_docbuild/ setup.py sage-setup sage_setup/ setup.py sage-sws2rst sage_sws2rst/ setup.py ... sagemath-standard bin/ sage -> ../../src/sage setup.py sage Script to start Sage src Monolithic Sage library source tree bin/ Scripts that Sage uses internally doc/ Sage documentation sources sage/ The Sage library source code VERSION.txt For more details see our Developer's Guide.