The development process of Python
summary
Summary lists concrete process and tools: core team is ~150+ developers with ~1,000+ contributors and ~2,800 open issues in Roundup; version control is Mercurial (hg) migration from SVN, commits are local and are exchanged by push/pull; workflows use multiple clones per branch and default / 3.x vs 2.7 branches for development and backports; every commit triggers buildbots that run the test suite across platforms; patches are submitted through the tracker, require review, include tests (run with -j and reference-leak checks), and are merged only after review.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:57Developers
- 9:42Mailing Lists (MLS)
- 14:39IRC channels
- 22:24Issue Tracker
- 38:01Mercurial (HG)
- 41:54Terms and concepts
- 44:04Differences with SVN
- 48:47Repo structure
- 49:47Status of the branches
- 53:23Merging order
- 54:27Basic usage
- 59:30Clones organization
related talks
36mWhat is a Python Core Developer?
41mHow to Grow an Open Source Project: A Case Study of Python
31mA reliable developmentrelease workflow for open source Python libraries
54mCore Python Devs on how COVID has changed core Python development
45mPython at Massive Scale
51mTaking Python beyond scripting
39mFireside Chat - Stewarding Rust & Python
43mHowto engage Python contributors in the long term?