Welcome to Tutorial to contribute to the CPython project’s documentation!

Contents:

• Getting Help
  • Active Core Developers
  • #python-dev channel
  • Core-mentorship mailing list
  • Developer Guide
  • Contributors
  • Looking for help on a specific Python module
  • Articles and talks about Python development
• Getting Started
  • Build CPython on Linux
  • Build CPython on Windows
  • Build CPython on macOS
• Contribute to CPython: where should I start?
• Python Community
  • Code Of Conduct
  • Diversity
  • CPython Communication Channels
• Run tests
  • Introduce a Bug
  • Run tests
  • Fix the bug
  • Run the whole test suite
• Write your first Python fix
  • How to find a bug or feature to write
  • Write the code
  • Add an unit test
  • Check for non-regression
• Write your first C fix
  • How to find a bug or feature to write
  • Write the code
  • Add an unit test
  • Check for non-regression
  • Check for reference leaks
• Open your first issue on bugs.python.org
  • Create your account
  • Open your issue
  • Bug fix
  • Feature request
• Write your first Pull Request
  • Create your GitHub account
  • Link your bugs.python.org account to your GitHub account
  • Sign the CLA
  • Create a local Git branch
  • Git remotes
  • Publish your pull request
• Lifetime of a change: bugs.python.org and PR updates
  • First, nothing happens
  • First feedback
  • Update your PR
• Review bugs and pull requests
• Propose new idea
• python-dev mailing list
• Continuous Integration (CI)
  • Travis CI
  • AppVeyor
  • Buildbots
• What is a CPython core developer?
  • python-committers
  • Who are core developers?
  • Different stages of core developers
  • New powers but also new responsibilities
  • Bug tracker
  • Mentoring
  • Requirements to become a core developer
  • Be patient
  • Vote to promote a contributor as a core developer
  • We Are All Volunteers
• Documentations of CPython internals

Indices and tables

• Index
• Module Index
• Search Page