4 ms·

I consider the CPython switch from Mercurial to git the final declaration of victory. I still have to understand how CPython could miss the symbolic meaning of

I consider the CPython switch from Mercurial to git the final declaration of victory. I still have to understand how CPython could miss the symbolic meaning of this decision.

mixmastamyk 11y ago
It's probably more accurate to say they switched to github, but yes.
marcinkuzminski 11y ago
imho for CPython, the decision was more of the network effect that Github have rather than picking any particular tool or language. I Know Gitlab was also taken into account, and RhodeCode as well which supported Mercurial and itself is also written in Python. I think in there days for large OS projects it's more important to have more potentials contributors rather than sticking to only Python projects. Just my 2c.
no__one 11y ago
More Guido and a couple of vocal people than CPython. I truly hope the switch wasn't the reason for Mackall to quit.
- durin42 11y ago
  Nope. mpm has been wanting to move on for a while, it's only recently that he's published plans more publicly.
ris 11y ago
"I consider the CPython switch from Mercurial to git the final declaration of victory." Really I think it was bitbucket's total sidelining of hg in favour of git. hg features break regularly on bitbucket and today if you visit bitbucket's home page you're greeted with "Bitbucket is the Git solution for professional teams"
rockdoe 11y ago
I'm not sure. I have the impression some larger organizations that are moving or using monolithic repos are now aligning more strongly towards hg, because it's easier to extend and optimize than Git. If you look at the outside contributions that both projects get, this is pretty obvious. Hg is getting big changes from Facebook, Google, Mozilla, ... Maybe the answer to the argument that a paradigm change is needed to unsettle git is simply "monolithic repos".

4 ms·

I consider the CPython switch from Mercurial to git the final declaration of victory. I still have to understand how CPython could miss the symbolic meaning of

by amadvance 11y ago

I consider the CPython switch from Mercurial to git the final declaration of victory. I still have to understand how CPython could miss the symbolic meaning of this decision.

mixmastamyk 11y ago
It's probably more accurate to say they switched to github, but yes.
marcinkuzminski 11y ago
imho for CPython, the decision was more of the network effect that Github have rather than picking any particular tool or language. I Know Gitlab was also taken into account, and RhodeCode as well which supported Mercurial and itself is also written in Python. I think in there days for large OS projects it's more important to have more potentials contributors rather than sticking to only Python projects. Just my 2c.
no__one 11y ago
More Guido and a couple of vocal people than CPython. I truly hope the switch wasn't the reason for Mackall to quit.
- durin42 11y ago
  Nope. mpm has been wanting to move on for a while, it's only recently that he's published plans more publicly.
ris 11y ago
"I consider the CPython switch from Mercurial to git the final declaration of victory." Really I think it was bitbucket's total sidelining of hg in favour of git. hg features break regularly on bitbucket and today if you visit bitbucket's home page you're greeted with "Bitbucket is the Git solution for professional teams"
rockdoe 11y ago
I'm not sure. I have the impression some larger organizations that are moving or using monolithic repos are now aligning more strongly towards hg, because it's easier to extend and optimize than Git. If you look at the outside contributions that both projects get, this is pretty obvious. Hg is getting big changes from Facebook, Google, Mozilla, ... Maybe the answer to the argument that a paradigm change is needed to unsettle git is simply "monolithic repos".