|
Size: 6655
Comment: link to GitHub for source code
|
← Revision 150 as of 2024-08-17 20:30:05 ⇥
Size: 4268
Comment: Update ReleaseTours link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| This is the wiki for the [[https://www.sagemath.org|Sage - Mathematics Software System]] project. This 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. | This is a wiki for the [[https://www.sagemath.org|Sage - Mathematics Software System]] project. There are other [[ThingsCalledSage]]. There is another [[https://github.com/sagemath/sage/wiki|Sage Wiki on GitHub]]. |
| Line 19: | Line 21: |
| == Sage Release Tours (version 9.0 and later) == * [[ReleaseTours]] |
|
| Line 30: | Line 28: |
| = Major external (editable) related pages = ||'''URL'''||'''Description'''|| ||[[https://www.sagemath.org/]]||Official homepage of SageMath|| ||[[https://trac.sagemath.org/]]||Where development happens|| ||[[https://pypi.org/project/sagemath/]]||dummy package on PyPi|| ||[[https://wiki.archlinux.org/index.php/SageMath]]||Arch Linux wiki|| |
|
| Line 39: | Line 30: |
| The most up-to date list of Sage developers is on our [[https://trac.sagemath.org/sage_trac/wiki#AccountNamesMappedtoRealNames|list of developers on the Sage trac wiki]]. | The most up-to date list of Sage developers is on our [[https://www.sagemath.org/development-map.html|Sage developer map]] |
| Line 41: | Line 32: |
| [[https://www.sagemath.org/development-map.html|Overview of (many) Sage developers on a world map]] | Some people still maintain their [[https://wiki.sagemath.org/CategoryHomepage|wiki homepages]]. |
| Line 45: | Line 36: |
| [[https://groups.google.com/group/sage-support|sage-support]], [[https://groups.google.com/group/sage-devel|sage-devel]], [[https://groups.google.com/group/sage-release|sage-release]], [[https://groups.google.com/group/sage-announce|sage-announcements]], [[https://groups.google.com/group/sage-edu|sage-edu]] for teaching using Sage, [[https://groups.google.com/group/sage-finance|sage-finance]] for finance, [[https://groups.google.com/group/sage-coding-theory|sage-coding-theory]] for coding theory, [[https://groups.google.com/group/sage-nt|sage-nt]] for number theory, and [[https://groups.google.com/group/sage-combinat-devel|sage-combinat-devel]]. | |
| Line 47: | Line 37: |
| [[https://zulip.sagemath.org | Zulip]] group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity but more than IRC. | The main active mailing lists are [[https://groups.google.com/group/sage-support|sage-support]], [[https://groups.google.com/group/sage-devel|sage-devel]], [[https://groups.google.com/group/sage-release|sage-release]]; see [[https://www.sagemath.org/development-groups.html |complete list of lists]]. |
| Line 49: | Line 39: |
| [[IRC]] channel: {{{#sagemath}}} on [[https://freenode.net/|freenode ]] (`chat.freenode.net`) | [[https://sagemath.zulipchat.com/|Zulip]] group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity. |
| Line 51: | Line 41: |
| The Sage website contains links to [[https://www.sagemath.org/development-groups.html | other discussion mailing lists]]. | !SageMath has a presence on some [[Social Networks]]. |
| Line 55: | Line 45: |
| Development is handled using "tickets" on the [[https://trac.sagemath.org/sage_trac/|trac server]]. | !SageMath development has moved to our [[https://github.com/sagemath/sage|GitHub repository sagemath/sage]]. |
| Line 57: | Line 47: |
| The main developer doc is the [[https://www.sagemath.org/doc/developer/ | Developers' Guide]]. Release notes (higher level than change logs) are collaboratively prepared at [[ReleaseTours]]. [[Infrastructure|Development/project infrastructure]] |
Release notes (higher level than change logs) are collaboratively prepared at [[https://github.com/sagemath/sage/wiki#release-tours|ReleaseTours]]. |
| Line 66: | Line 52: |
| * [[Debate/Collective infrastructure management]] | |
| Line 69: | Line 54: |
| * [[asksage retagging]] * [[Conda|Using Conda to build SageMath]] |
|
| Line 72: | Line 55: |
= Features = |
= Features and Packages = |
| Line 76: | Line 58: |
| * [[SageMathExternalPackages|Packages included with SageMath and external packages]] | |
| Line 81: | Line 64: |
| * [[interactive|Interactive Visualization]] | |
| Line 82: | Line 66: |
= 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]] == Obsolete, duplicate, outdated == * [[spkg|SageWiki page "spkg"]] - now just links to the spkg section of the reference manual * [[http://www.sagemath.org/links-components.html|sagemath.org page "Components"]] - now just links to the spkg section of the reference manual * everything about old-style SPKGs - outdated, do not use |
|
| Line 120: | Line 69: |
| '''Editing the wiki.''' Page editing uses the MoinMoin syntax. To edit the wiki, log in using your [[https://trac.sagemath.org/sage_trac/|sage-trac]] account. Getting an account involves convincing a human by email that you not a spammer. | '''Editing the wiki.''' Page editing uses the MoinMoin syntax. If you want to edit the wiki or change your password, do not hesitate to request an account by sending an email at wikisage@lma.metelu.net; 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 122: | 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://github.com/sagemath/sage/issues/33725|Pages related to development are being transferred to the Sage Wiki on GitHub or merged in our developer guide.]] |
SageMath Wiki
This is a wiki for the Sage - Mathematics Software System project. There are other ThingsCalledSage.
There is another Sage Wiki on GitHub.
❤ |
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 127 -- TU Vienna, Austria (February 22-25, 2025); theme: using SageMath for Algebra, Combinatorics, and Probability
Sage Days 128 — combinatorics, number theory, dynamical systems and geometry, February 10-14, 2025, Le Teich, near Bordeaux, France
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 Sage developer map
Some people still maintain their wiki homepages.
Mailing Lists / Chat Rooms
The main active mailing lists are sage-support, sage-devel, sage-release; see complete list of lists.
Zulip group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity.
SageMath has a presence on some Social Networks.
Development
SageMath development has moved to our GitHub repository sagemath/sage.
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. If you want to edit the wiki or change your password, do not hesitate to request an account by sending an email at wikisage@lma.metelu.net; 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 Sage Wiki on GitHub or merged in our developer guide.
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.