PyPy Moves To GitHub (Posting On Python-List Prohibited)
Lawrence D'Oliveiro <[email protected]>
| Newsgroups | comp.lang.python |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
So the PyPy project is moving away from using Mercurial for version control, and embracing Git and GitHub <https://devclass.com/2024/01/02/pypy-moves-from-mercurial-says-open-source-has-become-synonymous-with-github/>. This report is yet another example of conflating Git and GitHub: you can use Git without also adopting GitHub-isms (like their strange meanings of “fork” and “pull”). Seems the main reason they liked Mercurial so much is its concept of “named branches”. But this doesn’t mean what you might think it means: it means that commits are always associated with a particular branch, unlike in Git where commits are just part of a chain, and a branch is simply a pointer to where new development is happening, not a record of where it happened before.