The devguide is now at https://github.com/python/devguide! Since I'm not waiting on the benchmarks repo while Victor Stinner does some perf measuring work, that means the cpython repo is next <queue dramatic music />.
If you look at https://www.python.org/dev/peps/pep-0512/#status you will see the list of issues that have to occur in order to migrate the cpython repo: 1. Update the devguide to document how we want to use git and GitHub ( https://github.com/python/devguide/milestone/1) 2. Link a PR to an issue (see http://psf.upfronthosting.co.za/roundup/meta/issue589) 3. Update an issue when a PR is closed (I believe http://psf.upfronthosting.co.za/roundup/meta/issue590 covers this) 4. Update hg.python.org/lookup to work with git hashes 5. Deprecate sys._mercurial and create sys._git ( http://bugs.python.org/issue27593) 6. Update PEP 101 Obviously help with any and all of this is appreciated and if you feel anything needs discussion then please start a new thread on the topic (and don't simply reply to this email so we can keep discussions separate).
_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
