# Sage **Devel**oper Center

Welcome to the Sage **devel**oper center!

Note: **Devel**opers should check trac.sagemath.org at least one per week. That's where **devel**opment actually happens.

TODO:

Organize, sage-**devel**.

Trac guidelines by Michael Abshoff

Cool tricks for better Firefox/trac integration

Docstring Docummentation for help on the format (ReSTructured text) used in the docstrings, including special Sage doctest conventions

Trac guidelines by Michael Abshoff

# Sage **devel**oper center

Welcome to the **Sage developer center**!

This wiki page helps in organizing the **devel**opment of Sage. Information and links to Sage **devel**opment should be organized under "**devel**/". For answers to commonly asked questions, see the FAQ.

Note: The trac server contains patches awaiting review. Michael Abshoff wrote a set of general guidelines for using the trac server. See also the **Devel**opers' Guide for further information on using the trac patch server.

Contents

# Release management

Each release cycle of Sage is managed by at least one release manager. For example, a release manager produces the various alpha and rc releases for the `sage-x.y.z` release cycle. Release management is a complex task. The release management page contains a rough set of guidelines for Sage release management. If you want to help out with release management, please subscribe to the sage-release mailing list.

# Sage **devel**opment

Much of the Sage library is written in Python. Some performance critical parts of the Sage library is written in Cython. Information is available to help beginners on **devel**oping the Sage library. Also consult the list of Python and Cython resources for beginner to advanced information on the Python and Cython languages. You can also do functional programming with Python and Sage. You should avoid as much as possible using non-ASCII characters in a source file. See this page for information on avoiding non-ASCII characters in source files. However, there are also cases in which you need put such characters in a source file. That page also has tips on specifying the character encoding of a source file. The page on docstring documentation contains information on the format (ReSTructured text) used in the docstrings of functions, classes, methods and modules. The page also includes special Sage doctest conventions. Before updating the copyright notices in the Sage library, read the page on copyright notices for a list of files to update as well.

If you have an account on the Sage cluster, ensure that you read the Sage cluster guidelines on using computer resources on the Sage cluster.

Please write Python3-compatible code (see Python3-compatible code) |

# Sage notebook

The legacy sage notebook is deprecated and not available under Python 3. |

Please use instead the Jupyter notebook. |

The Sage notebook provides a graphical user interface to Sage. To help out with **devel**oping the Sage notebook, you need to know how to code in JavaScript. The page on JavaScript resources contains many resources on JavaScript and JavaScript libraries. The Sage notebook technical overview provides a technical overview of the Sage notebook server, including how it responds to user requests, delegates tasks, etc. See also the page on usability improvements for a list of **devel**opment tasks relating to enhancing the notebook and its usability. See the page on Sage notebook internationalization for a list of available locales, and instructions on how to make one.

# Miscellaneous

Cool tricks for better Firefox/trac integration