Important

Did this article help?

We are currently doing research to improve pip’s documentation and would love your feedback. Please email us &body=%0A%20%20%20%200.%20Document:%20development/index.%20Page%20URL:%20https:/%20%0A%0A%20%20%20%201.%20What%20problem%20were%20you%20trying%20to%20solve%20when%20you%20came%20to%20this%20page?%20%0A%0A%20%20%20%202.%20What%20content%20was%20useful?%20%0A%0A%20%20%20%203.%20What%20content%20was%20not%20useful?) and let us know why you came to this page and what on it helped you and what did not. (Read more about this research)

Development

pip is a volunteer maintained open source project and we welcome contributions of all forms. The sections below will help you get started with development, testing, and documentation.

You can also join #pypa (general packaging discussion and user support) and #pypa-dev (discussion about development of packaging tools) on Freenode, or the distutils-sig mailing list, to ask questions or get involved.

• Getting Started
  • Get the source code
  • Development Environment
  • Running pip From Source Tree
  • Running Tests
  • Running Linters
  • Building Documentation
  • What Next?
• Contributing
  • Pip’s internals
  • Submitting Pull Requests
  • Automated Testing
  • NEWS Entries
  • Updating your branch
  • Becoming a maintainer
• Continuous Integration
  • Supported interpreters
  • Checks
  • Services
  • Current run tests
• Issue Triage
  • Issue Tracker
  • Triage Issues
  • Common issues
• Architecture of pip’s internals
  • Broad functionality overview
  • Repository anatomy & directory structure
  • Configuration File Handling
  • Finding and choosing files (index and PackageFinder)
  • Command Line Interface
  • Options that control the installation process
• Release process
  • Release Cadence
  • Deprecation Policy
  • Feature Flags
  • Release Process
• Vendoring Policy
  • Rationale
  • Modifications
  • Automatic Vendoring
  • Debundling

Note

pip’s development documentation has been rearranged and some older references might be broken.

Important

Did this article help?

We are currently doing research to improve pip’s documentation and would love your feedback. Please email us &body=%0A%20%20%20%200.%20Document:%20development/index.%20Page%20URL:%20https:/%20%0A%0A%20%20%20%201.%20What%20problem%20were%20you%20trying%20to%20solve%20when%20you%20came%20to%20this%20page?%20%0A%0A%20%20%20%202.%20What%20content%20was%20useful?%20%0A%0A%20%20%20%203.%20What%20content%20was%20not%20useful?) and let us know:

1. What problem were you trying to solve when you came to this page?

2. What content was useful?

3. What content was not useful?