|
Size: 1931
Comment:
|
Size: 6722
Comment: link to ThingsCalledSage
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Before his entrance into politics, the name of Coriolanus evoked awe. His battlefield accomplishments showed him as a man of great bravery - something which we can learn and integrate into our job interview tips. Since the citizens knew little about him, all kinds of legends became attached to his name. The moment he appeared before the Roman citizens, however, and spoke his mind, all that grandeur and mystery vanished. He bragged and blustered like a common soldier. He insulted and slandered people, as if he felt threatened and insecure. Suddenly he was not at all what the people had imagined. The discrepancy between the legend and the reality proved immensely disappointing to those who wanted to believe in their hero. The more Coriolanus said, the less powerful he appeared - a person who cannot control his words shows that he cannot control himself, and is unworthy of respect. When it comes to your interview, remember this piece of job interview advice - don't oversell yourself, and know when to stop talking and let the other side have their say. | = SageMath Wiki = |
| Line 3: | Line 3: |
| Had Coriolanus listened to his mentor's job interview advice and said less, the people would never have had cause to be offended by him, would never have known his true feelings. He would have maintained his powerful aura, would certainly have been elected consul, and would have been able to accomplish his antidemocratic goals. But the human tongue is a beast that few can master. It strains constantly to break out of its cage, and if it is not tamed, it will run wild and cause you grief. Power cannot accrue to those who squander their treasure of words. | This is the wiki for the [[https://www.sagemath.org|Sage - Mathematics Software System]] project. There are other [[https://wiki.sagemath.org/ThingsCalledSage]]. |
| Line 5: | Line 5: |
| Oysters open completely when the moon is full; and when the crab sees one it throws a piece of stone or seaweed into it and the oyster cannot close again so that it serves the crab for meat. Such is the fate of him who opens his mouth too much and thereby puts himself at the mercy of the listener. | 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. ||<tablestyle="font-size: 0.8em;">||<#F7819F>❤ || You can help by becoming a [[https://github.com/sponsors/sagemath|sponsor]]|| ||<tablestyle="font-size: 0.8em;">||<#74DF00>Information || Since version 9.0, Sage is using '''Python 3'''. See [[Python3-Switch]] for more information.|| <<TableOfContents>> = SageDays, Sage Workshops, other activities = <<Anchor(sagedays)>> == Past and future Workshops == * Upcoming Workshops <<Include(Workshops, , from="^##start-include$", to="^----$")>> * [[Workshops | All Workshops]], including past and future Sage Days, Bug Days, Doc Days, Review Days, Education Days, and some other Sage-related events. == Sage Release Tours (version 9.0 and later) == * [[ReleaseTours]] == Google Summer of Code == * [[GSoC|Google Summer of Code]] == Hosting a workshop == * [[HowToHostASageDays|How To Host A Sage Days]] --- Advice to future hosts * [[HowToSpreadSageDuringAWorkshop|How to Spread Sage During a Workshop]] --- Advice to future hosts = 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|| = People = 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]]. [[https://www.sagemath.org/development-map.html|Overview of (many) Sage developers on a world map]] <<Anchor(messagingsites)>> = Mailing Lists / Chat Rooms = [[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]]. [[https://zulip.sagemath.org | Zulip]] group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity but more than IRC. [[IRC]] channel: {{{#sagemath}}} on [[https://freenode.net/|freenode ]] (`chat.freenode.net`) The Sage website contains links to [[https://www.sagemath.org/development-groups.html | other discussion mailing lists]]. = Development = 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]]. Release notes (higher level than change logs) are collaboratively prepared at [[ReleaseTours]]. [[Infrastructure|Development/project infrastructure]] = Special Discussion Pages = * [[Coding_Theory|Coding Theory in Sage]] * [[Debate/Collective infrastructure management]] * [[Python3-compatible code|Writing Python 3 compatible code]] * [[OptiPolyGeom|Optimization and Polyhedral Geometry in Sage]] * [[asksage retagging]] * [[Conda|Using Conda to build SageMath]] = Features = * [[http://www.sagemath.org/tour.html|sagemath.org: SageMath Feature Tour]] * [[Interfaces|Sage wiki: SageMath interfaces to and from other software]] == Demonstrations of Graphical Capabilities == * [[art|Art - posters, banners, etc]] * [[interact|Interact Demos]] * [[K3D-tools|K3D-jupyter 3D visualisation in jupyter notebook]] = 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 = About this wiki = '''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. '''SageWiki maintenance.''' The [[SageWikiMaintenance page]] attempts to reorganize the wiki, which has accumulated many outdated pages. '''License and Copyright.''' Contributions to the [[https://www.sagemath.org/|Sage]] wiki and to the [[https://doc.sagemath.org|Sage documentation]] are licensed under the [[https://creativecommons.org/licenses/by-sa/3.0/|Creative Commons 3.0 BY-SA license]]. By contributing, you agree to place your contribution under that license. |
SageMath Wiki
This is the wiki for the Sage - Mathematics Software System project. There are other https://wiki.sagemath.org/ThingsCalledSage.
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.
❤ |
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.
Sage Release Tours (version 9.0 and later)
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
Major external (editable) related pages
URL |
Description |
Official homepage of SageMath |
|
Where development happens |
|
dummy package on PyPi |
|
Arch Linux wiki |
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 but more than IRC.
IRC channel: #sagemath on freenode (chat.freenode.net)
The Sage website contains links to other discussion mailing lists.
Development
Development is handled using "tickets" on the trac server.
The main developer doc is the Developers' Guide.
Release notes (higher level than change logs) are collaboratively prepared at ReleaseTours.
Development/project infrastructure
Special Discussion Pages
Features
Demonstrations of Graphical Capabilities
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 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 Developer's Guide.
Since Sage 9.2, the spkg section of the Sage reference manual is automatically generated from the information in SAGE_ROOT/build/pkgs/. (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
Obsolete, duplicate, outdated
SageWiki page "spkg" - now just links to the spkg section of the reference manual
sagemath.org page "Components" - now just links to the spkg section of the reference manual
- everything about old-style SPKGs - outdated, do not use
About this wiki
Editing the wiki. Page editing uses the MoinMoin syntax. To edit the wiki, log in using your sage-trac account. Getting an account involves convincing a human by email that you not a spammer.
SageWiki maintenance. The SageWikiMaintenance page attempts to reorganize the wiki, which has accumulated many outdated pages.
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.