Helping with documentation

devguide.python.org

Tin mới

Setup and building

Fixing “easy” issues (and beyond)

Git bootcamp and cheat sheet

Lifecycle of a pull request

Guidelines for using AI tools

Following Python’s development

Adding to the stdlib

Standard library extension modules

Changing Python’s C API

Changing CPython’s grammar

Porting and platform support

Using the issue tracker

reStructuredText markup

Helping with the Developer’s Guide

Running and writing tests

Silence warnings from the test suite

Increase test coverage

OSS-Fuzz for CPython

Working with buildbots

New buildbot workers

Dynamic analysis with Clang

Tools for tracking compiler warnings

Accepting pull requests

Motivations and affiliations

How to join the core team

Python Security Response Team (PSRT)

Software Bill-of-Materials (SBOM)

Documenting Python

Python is known for having well-written documentation. Maintaining the documentation’s accuracy and keeping a high level of quality takes a lot of effort. Community members, like you, help with writing, editing, and upda

Python documentation¶

Python is known for having well-written documentation. Maintaining the documentation’s accuracy and keeping a high level of quality takes a lot of effort. Community members, like you, help with writing, editing, and upda

Quick Guide to Pull Requests

Python is known for having well-written documentation. Maintaining the documentation’s accuracy and keeping a high level of quality takes a lot of effort. Community members, like you, help with writing, editing, and upda

Python documentation¶

Python is known for having well-written documentation. Maintaining the documentation’s accuracy and keeping a high level of quality takes a lot of effort. Community members, like you, help with writing, editing, and upda