That said, I also plan to keep my core projects on 2.x for a few more months till django, ipython, debian repos etc. move to 3.x. But I do plan to play with 3.x some.
I have a svn (1.5.x) repository on my server and use bzr-svn to access it. I and another developer push our changes to the server at logical points. On the server we have a simple svn workspace which we update when we want to publish our changes.
Works quite nicely. Also, you have the flexibility of using the regular svn client.
I haven't tried working with the 100% distributed solution as the current solution works. As there are only two developers we don't really have much need for branching.
If you want to use a DVCS you could also consider bzr (apart from git and hg).
I am more of a bzr and svn user. Both work quite nicely for me. I haven't really used git on a project.
I know git performance is much much better than bzr but as thats not a major concern for small/medium projects, could someone who has used both bzr and git give some pointers on what one would be nicer to use than the other in areas other than performance?
From the release page (http://www.python.org/download/releases/3.0/): This is a production release; we currently support these formats: ...
That said, I also plan to keep my core projects on 2.x for a few more months till django, ipython, debian repos etc. move to 3.x. But I do plan to play with 3.x some.