Python moved to GitHub

Python and GitHub logo

This PEP outlines the steps required to migrate Python’s development process from Mercurial as hosted at hg.python.org to Git on GitHub. Meeting the minimum goals of this PEP should allow for the development process of Python to be as productive as it currently is, and meeting its extended goals should improve the development process from its status quo.

Visit Python on GitHub here

Rationale

In 2014, it became obvious that Python’s custom development process was becoming a hindrance. As an example, for an external contributor to submit a fix for a bug that eventually was committed, the basic steps were:

1. Open an issue for the bug at bugs.python.org [5].
2. Checkout out the CPython source code from hg.python.org.
3. Make the fix.
4. Upload a patch.
5. Have a core developer review the patch using our fork of the Rietveld code review tool.
6. Download the patch to make sure it still applies cleanly.
7. Run the test suite manually.
8. Update the NEWS, ACKS, and “What’s New” document as necessary
9. Pull changes to avoid a merge race.
10. Commit the change manually.
11. If the change was for a bugfix…