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/architecture/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)

Architecture of pip’s internals

Note

This section of the documentation is currently being written. pip developers welcome your help to complete this documentation. If you’re interested in helping out, please let us know in the tracking issue, or just go ahead and submit a pull request and mention it in that tracking issue.

Note

Direct use of pip’s internals is not supported, and these internals can change at any time. For more details, see Using pip from your program.

• Broad functionality overview
  • Broad overview of flow
• Repository anatomy & directory structure
  • Root and tools
  • src directory
• Configuration File Handling
  • Overview
  • Configuration class
  • kinds
  • Future Refactoring Ideas
• Finding and choosing files (index and PackageFinder)
  • Overview
  • The PackageFinder class
  • The LinkCollector class
  • The LinkEvaluator class
  • The CandidateEvaluator class
  • The CandidatePreferences class
  • The BestCandidateResult class
• Command Line Interface
  • Overview
  • Future Refactoring Ideas
• Options that control the installation process
  • Controlling what gets installed
  • Controlling what gets considered
  • Controlling dependency data
  • Special cases

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/architecture/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?