News for hackers. Stuff that matters.
Re:Python switching to Mercurial by w1ntermute on Monday March 30, 2009 @12:22PM (#538694)
"At PyCon, Brett already announced that Git was no longer being considered -- while it has obviously many fans, it also provokes strong antipathies."

This seems illogical at best. They chose not to use Git because there are a lot of people that dislike it? This decision should have been based on technical details, not on feelings. Anything else is doing a disservice to the developers and to the community. How many other VCS's were passed up because they had a lot of haters?

Re:Python switching to Mercurial by mrz on Monday March 30, 2009 @12:25PM (#538699)
I guess the feelings are based on technical details.
Re:Python switching to Mercurial by LargeWu on Monday March 30, 2009 @01:19PM (#538781)
Just looking at the python/ruby communities mostly from the outside, I wouldn't discount that many python folks dislike Git simply because many rubyists like it. I'm not saying there aren't valid technical reasons, (and frankly I don't know much technically about either Git or Mercurial) but I'd be surprised if emotion/religion doesn't play in at least a little bit.
Re:Python switching to Mercurial by erlanger on Monday March 30, 2009 @02:29PM (#538893)
That's a good point. Ruby has really become Python's "Other" in spite of their similarities.
Re:Python switching to Mercurial by w1ntermute on Monday March 30, 2009 @03:36PM (#538999)
You "guess"? That's not a very accurate analysis of the situation.

Since they aren't sharing any of these details, we have no choice but to assume there are none. In fact, their exact reason for not using Git was "it also provokes strong antipathies". That doesn't even _imply_ technicality on any level.

Either way, I couldn't care less personally. The only people they're hurting are themselves, as a gateway can be created between Git and Mercurial. All the projects I work on right now use SVN, and I just use git-svn for everything.

Re:Python switching to Mercurial by pjhyett on Monday March 30, 2009 @02:28PM (#538891)
I'm not sure why you're being down-modded.

The Python team purporting to do DVCS research and then saying their decision was made on a gut feeling seems disingenuous at best.

Sure, I'm biased because I work for GitHub, but this decision would have felt like much less of a slap in the face had they just said: "We're switching to Mercurial because we like it and it's written in Python, case closed."

Re:Python switching to Mercurial by etal on Monday March 30, 2009 @03:47PM (#539017)
The way I read it, and the document discussing the VCS switch (PEP 374), was that the Big Three DVCSes (git, hg, bzr) were essentially all just fine. Git is the fastest and hairiest, Bazaar is the slowest and cutest, and Mercurial covers both ends fairly well without introducing any glaring flaws. All three systems have big, well-known projects actively running on them, with developers singing about how much better their respective choices are compared to the SVN or CVS systems. Any choice would have been fine; it was fairly obvious.

Python has a history of fussy programmers. Remember the web framework wars of a few years ago? Everyone complained that there were too many choices, picked favorites to champion and nitpicked at the alternatives (which were not actually bad), and nobody could sleep at night because there were alternatives and nobody knew which one was right. Then Guido announced that Django was right, and the lost souls breathed a sigh of relief and did the Django tutorial, and the folks who were already using Turbogears and Pylons productively continued to do so. Django isn't necessarily the best Python web framework for everyone, but it's rarely a bad choice.

That's pretty much what happened this year with DVCSes. The Biopython project was stalled on a CVS-to-SVN transition for over a year, for example, until some grenades were thrown and tears were shed and finally Git was picked because a few people liked it, nobody really had a problem with it and all the other options were triggering nasty blog posts. Case closed. Sometimes we just need a quick slap to shut us up.

Re:Python switching to Mercurial by bendotc on Monday March 30, 2009 @02:52PM (#538930)
If you read much of what Guido writes, you'll see that most of his decisions come from a lot of thinking about a topic or problem and then going with what his gut tells him. It just seems to be the way he works, and I'd argue that the results speak for themselves.

And I can understand how you would wish they used git, but if you're taking this as a "slap in the face" at all, I think you're reading it wrong. They did some research on various similar tools and picked one.

Re:Python switching to Mercurial by jmtulloss on Monday March 30, 2009 @01:49PM (#538825)
Why would you ever force a system that nobody likes on your developers? "Better" doesn't matter if nobody's happy using it.
Re:Python switching to Mercurial by w1ntermute on Monday March 30, 2009 @03:41PM (#539008)
He didn't say that the developers in particular didn't like it. He didn't even say that _he_ doesn't like it. He only gave a generic statement referring to an unknown group of people.

My problem is not with their decision, but with how they made it. They are taking the "cathedral" approach, rather than the "bazaar" one.

Re:Python switching to Mercurial by SwellJoe on Tuesday March 31, 2009 @12:56PM (#540383)
He didn't say that the developers in particular didn't like it. He didn't even say that _he_ doesn't like it. He only gave a generic statement referring to an unknown group of people.

Also known as "weasel words": http://en.wikipedia.org/wiki/Weasel_word

Re:Python switching to Mercurial by run4yourlives on Monday March 30, 2009 @01:20PM (#538784)
Conversely, do you feel they should make decisions based on the number of developers that do like a system?