I had initially suggested hg-git, but after my (mostly negative) experience in trying to convert the CPython repo, my vote goes towards fast-export. Partly because it's the only once *specifically* designed for exporting, not trying to be a bridge like hg-git and the other tool.

[ERROR]: Your autotools build scripts are 200 lines longer than your program. Something’s wrong.

On Apr 22, 2016 6:27 PM, "Brett Cannon" <brett@python.org> wrote:
Now that I'm comfortable declaring the code for the CLA bot finished (https://github.com/python/the-knights-who-say-ni), the next step is to finalize the command(s) we are going to use to convert hg repositories to git for migration to GitHub. Senthil, are you ready to make a final decision?

Once I have the conversion command(s) documented in PEP 512 and I have created the "Python core" team on GitHub for all of the current Python core developers, I will migrate https://hg.python.org/devinabox to make sure that everything works. After that has been verified as working I will then look at migrating https://hg.python.org/devguide/ and https://hg.python.org/peps/ (will take a little bit more effort for both to get the web builds updated, and peps requires getting the PEP editors on-board). The benchmarks repo might actually not get migrated as there is talk of starting that repo from scratch.

It's looking like we will stay on track to get at least one repository migrated by PyCon US!

core-workflow mailing list
This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct