Re: [core-workflow] Help needed: best way to convert hg repos to git?

Response from GitHub staff regarding using their Importer to import CPython: Unfortunately, the repository is too large to migrate using the importer. I’d recommend converting it to git locally using something like hg-fast-export. Due to its size, you’ll need to push

Re: [core-workflow] Help needed: best way to convert hg repos to git?

> I'm currently trying to import to see how it looks, have been stuck at 0% for a few minutes now. Doing the same myself. Got to 73% and it restarted. Am back at 73% now. Already reached out to GitHub to make them aware of the issue. Will report here when/if I have results. Nick

Re: [core-workflow] My initial thoughts on the steps/blockers of the transition

We can set a commit status that will show red if the user hasn’t signed the CLA (just like if Travis tests failed or so). No need to use a banner or anything. This is a great idea. Almost any automated check we want to run against PRs can be captured as a Travis/CI test that shows up on the PR

Re: [core-workflow] Standard library separation from core (was Re: My initial thoughts on the steps/blockers of the transition)

uary 2016 at 12:50, Nicholas Chammas <nicholas.cham...@gmail.com> > wrote: > > Something else to consider. We’ve long talked about splitting out the > stdlib > > to make it easier for the alternative implementations to import. If some > or > > all of them also swi