|
Size: 6163
Comment: Remove "major external pages"
|
Size: 4642
Comment: Reduce duplicated development material
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
This wiki is mainly used by developers for organization of e.g. SageDays and discussion of long-term projects. Since it ''is'' a wiki, pages should be made to last over many, and frequent, changes. If an external link is made, please attach relevant files/content to avoid broken links. |
|
| Line 20: | Line 18: |
== Sage Release Tours (version 9.0 and later) == * [[ReleaseTours]] |
|
| Line 50: | Line 44: |
| Development is handled using "tickets" on the [[https://trac.sagemath.org/sage_trac/|trac server]]. The main developer doc is the [[https://www.sagemath.org/doc/developer/ | Developers' Guide]]. |
See [[https://trac.sagemath.org/sage_trac/|SageMath Development Organization Page]] on the Sage Trac server. |
| Line 55: | Line 47: |
[[Infrastructure|Development/project infrastructure]] |
|
| Line 65: | Line 55: |
| * [[Conda|Using Conda to build SageMath]] | |
| Line 67: | Line 56: |
= Features = |
= Features and Packages = |
| Line 71: | Line 59: |
| * [[SageMathExternalPackages|Packages included with SageMath and external packages]] | |
| Line 78: | Line 67: |
| = Packages = == New-style SPKGs == There is a single authoritative place to learn about the specific set of packages (new-style SPKGs) that Sage uses: The [[https://github.com/sagemath/sage/tree/develop/build/pkgs|SAGE_ROOT/build/pkgs/]] directory in the Sage distribution. Each SPKG is represented by a subdirectory. The structure of these subdirectories is explained in the [[https://doc.sagemath.org/html/en/developer/packaging.html|Developer's Guide|]]. Since Sage 9.2, the [[https://doc.sagemath.org/html/en/reference/spkg/|spkg section of the Sage reference manual]] is automatically generated from the information in `SAGE_ROOT/build/pkgs/`. ([[https://trac.sagemath.org/ticket/29655|Trac #29655]] improves the formatting of this information.) Use the following shell commands below to access the information from the `SAGE_ROOT/build/pkgs` directory of your copy of Sage: * Standard packages: `./sage -standard` * Installed packages: `./sage -installed` * Optional packages available: `./sage -optional` * Experimental packages available: `./sage -experimental` * Details about an SPKG: `./sage -info <SPKG>` For some advanced package tools, use `./sage -package` == External packages == * SageMathExternalPackages * [[CodeSharingWorkflow|On development models for sharing (experimental) code]] |
|
| Line 109: | Line 69: |
| '''Editing the wiki.''' Page editing uses the MoinMoin syntax. To edit the wiki, you will need a log in using your [[https://trac.sagemath.org/#legacy-account-request|legacy sage-trac account]] account; a !GitHub account cannot be used for this. If you edit an existing page with a long history, a key question is: "If someone opens this page tomorrow, will they be able to tell which information is current and which is outdated?" Edit accordingly. | '''Editing the wiki.''' Page editing uses the MoinMoin syntax. To edit the wiki, you will need a log in using your [[https://trac.sagemath.org/#legacy-account-request|legacy sage-trac account]] account; a !GitHub account cannot be used for this. Since it ''is'' a wiki, pages should be made to last over many, and frequent, changes. If an external link is made, please attach relevant files/content to avoid broken links. If you edit an existing page with a long history, a key question is: "If someone opens this page tomorrow, will they be able to tell which information is current and which is outdated?" Edit accordingly. |
| Line 111: | Line 71: |
| '''SageWiki maintenance.''' The [[SageWikiMaintenance page]] attempts to reorganize the wiki, which has accumulated many outdated pages. | '''SageWiki maintenance.''' The [[SageWikiMaintenance page]] attempts to reorganize the wiki, which has accumulated many outdated pages. [[https://trac.sagemath.org/ticket/33725|Pages related to development are being transferred to the Trac wiki.]] |
SageMath Wiki
This is the wiki for the Sage - Mathematics Software System project. There are other ThingsCalledSage.
❤ |
You can help by becoming a sponsor |
Information |
Since version 9.0, Sage is using Python 3. See Python3-Switch for more information. |
Contents
SageDays, Sage Workshops, other activities
Past and future Workshops
- Upcoming Workshops
Sage Days 124.7 — Sessions at the 8th International Congress on Mathematical Software, July 22-25, 2024, Durham (UK)
Sage Days 125 — combinatorics, number theory, dynamical systems and geometry, January 29th - February 1st, 2024, Le Teich, near Bordeaux, France
Sage Days 126 - August 31-September 2, 2024, Chennai, India
All Workshops, including past and future Sage Days, Bug Days, Doc Days, Review Days, Education Days, and some other Sage-related events.
Google Summer of Code
Hosting a workshop
How To Host A Sage Days --- Advice to future hosts
How to Spread Sage During a Workshop --- Advice to future hosts
People
The most up-to date list of Sage developers is on our list of developers on the Sage trac wiki.
Overview of (many) Sage developers on a world map
Mailing Lists / Chat Rooms
sage-support, sage-devel, sage-release, sage-announcements, sage-edu for teaching using Sage, sage-finance for finance, sage-coding-theory for coding theory, sage-nt for number theory, and sage-combinat-devel.
Zulip group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity.
SageMath has a presence on some Social Networks.
The Sage website contains links to other discussion mailing lists.
Development
See SageMath Development Organization Page on the Sage Trac server.
Release notes (higher level than change logs) are collaboratively prepared at ReleaseTours.
Special Discussion Pages
Features and Packages
Demonstrations of Graphical Capabilities
About this wiki
Editing the wiki. Page editing uses the MoinMoin syntax. To edit the wiki, you will need a log in using your legacy sage-trac account account; a GitHub account cannot be used for this. Since it is a wiki, pages should be made to last over many, and frequent, changes. If an external link is made, please attach relevant files/content to avoid broken links. If you edit an existing page with a long history, a key question is: "If someone opens this page tomorrow, will they be able to tell which information is current and which is outdated?" Edit accordingly.
SageWiki maintenance. The SageWikiMaintenance page attempts to reorganize the wiki, which has accumulated many outdated pages. Pages related to development are being transferred to the Trac wiki.
License and Copyright. Contributions to the Sage wiki and to the Sage documentation are licensed under the Creative Commons 3.0 BY-SA license. By contributing, you agree to place your contribution under that license.