devguide
devguide copied to clipboard
The Python developer's guide
The `triaged` label was recently added, and should be documented. See: * https://github.com/python/core-workflow/issues/465 * https://github.com/python/steering-council/issues/130 * https://discuss.python.org/t/improve-communication-with-contributors-on-the-issue-tracker-and-prs-language-summit-follow-up/15812/30 I can take care of this while updating the other labels (see #821).
Moved from https://github.com/python/cpython/issues/58426
We currently have several lists of developers, some manually maintained, some machine-generated, including: * a machine-parsable list in the voters repo (private) * a machine-generated (from the list above) [developers.csv](https://github.com/python/devguide/blob/main/core-developers/developers.csv)...
**Describe the enhancement or feature you'd like** The devguide does not contain information what a triager and core dev has to do when adding files or non-trivial portions of code...
On python/cpython#94636 , specifically https://github.com/python/cpython/pull/94636#discussion_r934008442 , @ezio-melotti , @erlend-aasland and I discussed that that it might be helpful to clarify in the devguide some additional guidance related to reference target...
I followed https://devguide.python.org/documenting/#without-make to build the docs without make: ``` sphinx-build -bhtml . build/html ``` It finished without error but nothing showed up under `build/` Wonder if it's just me....
This is a follow-up of #727 and related to #681. Since `make linkcheck` is somewhat unreliable and can't be required for regular PR, the idea is to use a workflow...
This PR fixes #883. I kept the Sphinx markup in the csv, or otherwise it would have been lost. The markup should be easy enough to remove while parsing, and...
Provide examples for managing the buildbot-worker service through systemd unit files for systemd based distributions.
In 2017, Victor added a useful tool to find failing tests, [bisect_cmd](https://github.com/python/cpython/blob/main/Lib/test/bisect_cmd.py), and [blogged about it](https://vstinner.github.io/python-test-bisect.html). I wish I knew about it before! IMO, the devguide should mention it.