Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.readnews.com!transit4.readnews.com!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: Version Control Software Date: Thu, 13 Jun 2013 17:06:59 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 29 Message-ID: References: <98c13a55-dbf2-46a7-a2aa-8c5f052ff375@googlegroups.com> NNTP-Posting-Host: dsl.comtrol.com X-Trace: reader1.panix.com 1371143219 436 64.122.56.22 (13 Jun 2013 17:06:59 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Thu, 13 Jun 2013 17:06:59 +0000 (UTC) User-Agent: slrn/1.0.1 (Linux) Xref: csiph.com comp.lang.python:47991 On 2013-06-13, Ben Finney wrote: > cutems93 writes: > >> I am looking for an appropriate version control software for python >> development, and need professionals' help to make a good decision. > >> Currently I am considering four software: git, SVN, CVS, and >> Mercurial. > > These days there is no good reason to use CVS nor Subversion for new > projects. They are not distributed (the D in DVCS), and they have > specific design flaws that often cause insidious problems with common > version control workflows. As a salient example, branching and merging > are so painful with these tools that many users have learned the > terrible habit of never doing it at all. I agree that branch/merge handling in svn is primitive compared to git (haven't used hg enough to comment). The last time we made the choice (4-5 years ago), Windows support for get, bzr, and hg was definitely lacking compared to svn. The lack of something like tortoisesvn for hg/git/bzr was a killer. It looks like the situation has improved since then, but I'd be curious to hear from people who do their development on Windows. -- Grant Edwards grant.b.edwards Yow! I wonder if there's at anything GOOD on tonight? gmail.com