SAGE
Programming Guide
Previous:
Front Matter
Up:
SAGE Programming Guide
Next:
1. Introduction
Contents
1. Introduction
2. How to create a SAGE module
2.1 Overview
2.2 Source Code Documentation
2.3 Extra Documentation
2.4 Randomized Testing
3. Conventions
3.1 File and directory names
3.2 Except
3.3 Docstrings
3.3.1 Further conventions for automated testing of examples
3.4 Optional packages
3.5 Special SAGE methods
3.5.1 Latex representation
3.5.2 Printing representation
3.5.3 Matrix from object
3.5.4 Vector from object
3.6 Heading
4. Testing
4.1 Testing .py, .pyx and .sage files
4.2 Testing LaTeX Documentation
5. The SAGE Documentation
5.1 Modifying the Tutorial
6. Adding Functionality to the PARI C-library Interface
7. Programming SAGE using GAP
8. Programming SAGE using Singular
8.1 Another Approach
8.2 Projects
9. Creating a SAGE Package
10. DARCS: The Revision Control System for SAGE
10.1 Getting started with DARCS
10.1.1 Resources
10.1.2 How to obtain DARCS
10.1.3 Do I have to install or configure ?
10.1.4 I need help
10.2 DARCS and SAGE
10.2.1 Quick start
10.2.2 Making changes
10.2.3 Compiling and running to test the patch
10.2.4 Making a patch bundle to send patches
10.2.5 Forgetting a patch: unpull
10.2.6 Receiving and applying a bundle
10.3 Upgrading and keeping up-to-date
10.3.1 Caution when upgrading with ``sage -upgrade"
10.3.2 Keeping the DARCS repo up-to-date
10.3.3 What to do with conflicts
10.4 Working with files
10.4.1 New files
10.4.2 Removing files
10.4.3 Renaming (moving) files
10.5 Tips and tricks
10.5.1 DARCS configuration
10.5.2 Forcing ``darcs apply" even with conflicts
10.6 Other useful commands to try
10.6.1 Other things to try
10.7 Important note on changing patches
11. Weird Issues
12. History and License
12.1 License
12.1.1 The GNU General Public License
Index
SAGE
Programming Guide
Previous:
Front Matter
Up:
SAGE Programming Guide
Next:
1. Introduction
Release 2006.05.25, documentation updated on May 25, 2006.
See
About this document...
for information on suggesting changes.