When I read yesterday night that Python 3.0 was imminent, I looked in awe at my calendar and thought “Is it already that late in the year”? This morning I then woke up, checked the newsfeeds and realized: Yes. Naturally this doesn’t mean that everyone will just leave 2.x behind and move over to 3.x right away but this public release hopefully makes it way more attractive to people to finally look into it then was the case with all these preview-builds ;-) And there’s much to look into, indeed:
-
A whole new way to handle strings (no longer do you distinguish between unicode strings and normal strings)
-
printis now a function and no longer a statement (which ended up in quite an ugly construct if you used it for printing to a specific IO-object) -
There is now only one integer type anymore. So
longgot dropped (andintis the newlong) -
sets and dict now also have their own *-comprehension shortcuts
and much much more. There are also some syntax changes, but from what I’ve seen so far Python stays Python :D
I’m not going to dive into it right away, but Graham Dumpleton also just wrote that mod_wsgi should already work with Python 3.0 with some tweaks if you’re using trunk.
Do you want to give me feedback about this article in private? Please send it to comments@zerokspot.com.
Alternatively, this website also supports Webmentions. If you write a post on a blog that supports this technique, I should get notified about your link 🙂