Remember python 3.0 is supposed to be an intermediate for migration release... not for production use. That's what 3.1 is for.
It's going to take ages for modules to get converted over... but most projects have been preparing for it for a while. However hopefully the migration scripts will get better over the 3.0 - 3.1 timeline.
For now I'm sticking with python 2.5 - since it's the best one considering it's far better module, and platform support.
> It's going to take ages for modules to get converted over...
You underestimate the power of the ... wait a sec. :)
Anyway, there's broad support and excitement in the community about this release. I think you'll see modules being updated more quickly than you suspect.
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.
Initially I was excited about 3.0 but as you pointed out it will take some time for modules to get converted over. I think this is very important. For me, one of the big selling points of Python is the large number of libraries written for it. With my luck I will need to use an obscure library that won't be updated any time soon by the author. So I'll have to stick with 2.5 or 2.6 because I need to get my job done rather than migrate a library.
It's sort of a chicken-and-egg problem because without widespread use of 3.0 no one will feel pressure to upgrade their library. I'm hoping, out of the goodness of their own hearts, that everyone will upgrade their libraries (for no immediate benefit but the gratitude of 3.0 users!). Maybe a website badge should be created for this accomplishment!
Python 3.0 includes a script that tries to automatically convert 2.6 code to 3.0 code, named 2to3. It's also incorporated into the package setup library, so in theory simply installing a Python 2.6 package with 3.0 will automatically convert the source code.
Of course, that means making your code work with 2to3 to begin with, but that's a much lower barrier to adoption than outright porting and dual maintenance.
It's going to take ages for modules to get converted over... but most projects have been preparing for it for a while. However hopefully the migration scripts will get better over the 3.0 - 3.1 timeline.
For now I'm sticking with python 2.5 - since it's the best one considering it's far better module, and platform support.