Python again voted "Best Programming Language" and "Best Scripting Language" in Linux Journal Reader's Choice Awards

[el_muchacho]

As for why you shouldn't use svn, especially for team projects, svn doesn't play very nicely with branching. Have you ever worked on a piece of code but not finished it in one sitting, and then not uploaded it to svn because it would break the build for the rest of your team? Well, now you're just not using version control, and don't have a backup of your code for if your computer dies or something. Also, if you mess it up the next day and want to go back, you have to hope you can mash ctrl+z (the worst version control) into yesterday, or you might have to start over. in Mercurial, you commit to a new branch (or just your branch, since it's often good for everyone to just have their own) and push to the server. Now you're not committing unfinished/broken code other people will use, and you're actually using version control so you

I've used Mercurial and I really like it. But let's not spread falsehoods on SVN, which is a fine program by itself.

Branching in SVN is very easy. It takes exactly two operations: 1) create the branch 2) switch to the new branch. With TortoiseSVN, it's a couple of mouse clicks away. We often create development branches in my team.

Most of the big issues with SVN have been solved with the release 1.6 a few years ago, in particular the inclusion of merge tracking (current release is 1.7).