Navigation

  • index
  • modules |
  • next |
  • previous |
  • pyengr 0.0.1+ documentation »

3. Managing a Python Software ProjectΒΆ

  • 3.1. Basic Version Control
    • 3.1.1. Initialization
      • 3.1.1.1. Install
      • 3.1.1.2. Configure
      • 3.1.1.3. Initialize a New Repository
      • 3.1.1.4. Repository File Layout
    • 3.1.2. Basic Concepts
      • 3.1.2.1. Graph of Changes
      • 3.1.2.2. Using the Help System of Mercurial
    • 3.1.3. Commit
      • 3.1.3.1. Adding New Files
      • 3.1.3.2. Modification of Files
      • 3.1.3.3. The Simplest Work Flow
    • 3.1.4. Ignorance
    • 3.1.5. Publish to Bitbucket
    • 3.1.6. Mercurial Queue
      • 3.1.6.1. Create a Patch
      • 3.1.6.2. Incremental Change
      • 3.1.6.3. Popping and Pushing Patches
      • 3.1.6.4. Finalization
    • 3.1.7. Other Topics
  • 3.2. Unit Tests
  • 3.3. Documentation
    • 3.3.1. Start a Sphinx Project with sphinx-quickstart
    • 3.3.2. Results of sphinx-quickstart
    • 3.3.3. Build the Document Project to HTML
    • 3.3.4. reStructuredText
    • 3.3.5. Documenting Python
    • 3.3.6. Mathematical Formula
    • 3.3.7. Using Third-Party Extensions (Optional)
  • 3.4. Management of Runtime and Dependencies
  • 3.5. Packaging and Distribution

Previous topic

2.5. Developing Python Extension Modules

Next topic

3.1. Basic Version Control

This Page

  • Show Source

Quick search

Enter search terms or a module, class or function name.

Navigation

  • index
  • modules |
  • next |
  • previous |
  • pyengr 0.0.1+ documentation »
© Copyright 2012, Yung-Yu Chen. Created using Sphinx 1.3.5.