One interesting thing from the "What's new in 3.2?"[1] page:<p>After the 3.2 release, there are plans to switch to Mercurial as the primary repository. This distributed version control system should make it easier for members of the community to create and share external changesets. See PEP 385 for details.<p>1- <a href="http://docs.python.org/dev/whatsnew/3.2.html" rel="nofollow">http://docs.python.org/dev/whatsnew/3.2.html</a>
Would someone to care to chime in on an estimate as to when it would be advisable for amateurs to start employing 3.x?<p>How far along are the libraries and the documentation/tutorials?
The concurrent.futures module looks interesting: <a href="http://docs.python.org/dev/whatsnew/3.2.html#pep-3148-the-concurrent-futures-module" rel="nofollow">http://docs.python.org/dev/whatsnew/3.2.html#pep-3148-the-co...</a><p>I don't have much experience in that area, so I can't judge if it's as cool as I think it is. Will anyone help me out?<p>The ability to safely convert string representations of data structures into the structures themselves seems pretty sweet, too: <a href="http://docs.python.org/dev/whatsnew/3.2.html#ast" rel="nofollow">http://docs.python.org/dev/whatsnew/3.2.html#ast</a>
Anybody done or know of any performance comparisons? Particularly intrigued by:<p><a href="http://docs.python.org/dev/whatsnew/3.2.html#multi-threading" rel="nofollow">http://docs.python.org/dev/whatsnew/3.2.html#multi-threading</a><p><a href="http://mail.python.org/pipermail/python-dev/2009-October/093321.html" rel="nofollow">http://mail.python.org/pipermail/python-dev/2009-October/093...</a>
If I could easily update python so that yum still worked fine on centos I would definitely start using python3. As it is I'm still stuck with python2.4 for a majority of the stuff I write.
Python 2.6 as a language is "good enough", for whatever meaning of that phrase. What would be exciting in Python development is the PyPy + LLVM (and the short stretch of the Unladen Swallow project) backend, and applying the modern optimization techniques for compiling dynamic code into efficient machine code. There is IronPython etc. but the platform is different from CPython's.
This is both wonderful and disappointing.<p>We're still pretty locked into 2.6. I'd love to move to 3.2 but it would break EVERYTHING!!!!(! added for emphasis!)<p>Maybe in ~10 years, everyone will be using 3.2, I know I can't wait! :D