CPython contribution guidelines
E888278
CPython contribution guidelines are the official rules and best practices that explain how to propose, develop, test, and submit changes to the core Python interpreter and standard library.
Statements (52)
| Predicate | Object |
|---|---|
| instanceOf |
software contribution guidelines
ⓘ
technical documentation ⓘ |
| alignedWith |
PEP 1
NERFINISHED
ⓘ
PEP 13 NERFINISHED ⓘ PEP 7 NERFINISHED ⓘ PEP 8 NERFINISHED ⓘ Python Enhancement Proposal process ⓘ |
| appliesTo |
CPython
NERFINISHED
ⓘ
Python interpreter ⓘ Python standard library NERFINISHED ⓘ |
| coversProcess |
developing patches for CPython
ⓘ
proposing changes to CPython ⓘ reviewing pull requests ⓘ submitting pull requests to CPython ⓘ testing changes to CPython ⓘ triaging issues ⓘ |
| defines |
backporting policy
ⓘ
bug triage workflow ⓘ deprecation policy ⓘ documentation contribution process ⓘ review process for CPython changes ⓘ roles of core developers ⓘ rules for merging pull requests ⓘ security issue handling process ⓘ |
| documentedIn | Python Developer’s Guide NERFINISHED ⓘ |
| goal |
ensure code quality in CPython
ⓘ
maintain consistency in CPython codebase ⓘ make contribution process transparent ⓘ reduce friction for new contributors ⓘ |
| hostedOn |
CPython Dev Guide
NERFINISHED
ⓘ
python.org NERFINISHED ⓘ |
| maintainedBy |
Python Steering Council
NERFINISHED
ⓘ
Python core developers ⓘ |
| recommends |
backwards compatibility consideration
ⓘ
clear commit messages ⓘ discussing large changes on python-dev or relevant mailing lists ⓘ following PEP 7 for C code ⓘ following PEP 8 for Python code ⓘ opening an issue on the CPython issue tracker before large changes ⓘ small, focused pull requests ⓘ using the CPython build and test tools ⓘ writing regression tests for bug fixes ⓘ |
| requires |
adding or updating tests for behavior changes
ⓘ
compliance with Python code style ⓘ running test suite ⓘ signed Contributor License Agreement ⓘ updating documentation for user-visible changes ⓘ |
| targetAudience |
Python core developers
ⓘ
experienced CPython contributors ⓘ new CPython contributors ⓘ |
| usesPlatform | GitHub NERFINISHED ⓘ |
| usesWorkflow | pull request based development ⓘ |
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.