I started learning Python in January after requesting the book "Dive Into Python 3" for Christmas. The lack of support for Python 3 on the web is highly frustrating, despite it being out for quite some time. Learning about the chicken and the egg scenario regarding why people have stuck with Python 2 has honestly left me a bit disillusioned after always hearing about what a great language it is.

That's just silly. 2.x, especially 2.6 and newer are still a fantastic choice. 3.x cleans up some ugliness, but isn't so superior that being stuck with 2.x would make ditching the language a viable choice.

You need to strike a balance between the bleeding edge and the pragmatic choice, and Python 2.x provides a _very_ good balance right now, which is why most of the interesting stuff is happening in that environment still.

I'm not thinking of ditching the language by any means. Even from the small amount I've learnt so far I think Python is amazing. It's just a bit frustrating at times when you're confused and unable to find much information about the problem you're having.

And really, I don't understand the point in learning an old version of a programming language. It just means I'm gonna have to wait it out like I have with so many other things.

Python 2.4 and above is not old version.

Python 3.x is just no SO great. Libraries, frameworks, wsgi matters.

3.x whenever possible, 2.x when libs require it.

I can't pick just one. (So I didn't vote.) I use both. I use Python mostly for scripts and small projects of a few hours' duration. Some projects are in 2, others are in 3. My most recent project switched from 3 to 2 halfway through. (I just had to change one call to print().)

2.x, for now. I'd like to switch to 3.x, but haven't found the time for it yet to figure out 2to3 and friends. Also, 2.x still has many more users, so any feasible open source product will have to still support 2.x anyway.

3.x, cause PyQt's come on it at last. Interpreter-wise, am used to the "print()" call already.

2.x is also available for emergency contributory/usage reasons though. (Although I end up printing tuples instead...)

Also note: 2.4 most of the time, despite the horrible waitForDeferred in Twisted (a side effect of a limited yield in 2.4), because RHEL 5.x variants still own the enterprise :(

Same same, everything I have been deploying to in the last month has 2.4 on it. I was told to "not try and shave that yak" when I enquired about going to 2.7.1

2.7.x and waiting for a few libs to be 3.x ready.

Currently using 2.6.5 for geoprocessing tasks in ArcGIS.

2.5 because of AppEngine. 2.7 when I get the choice.

Using archlinux,both 2.7 and 3.1 are installed.