Python 3000 Status Update from Guido

I just stumbled on this and I thought I’d pass it onto my fellow python programmers, it’s a python 3000 status update from Guido van Rossum.

Personally I’m looking forward to Python 3.0, I don’t know if I’ll like the break in backwards compatibility but a lot of the changes seem great.

Making the print statement a function is a good choice in my opinion.

So instead of:

[code lang=”python”]
print “this is printing”

We’ll be using:

[code lang=”python”]
print(“this is python 3.0”)

Also instead of % to format strings, there will be a format() function, which is so much clearer in my opinion.

There are many other changes (say goodbye to old-style classes) so give the link a read and let me know what you think!

3 thoughts on “Python 3000 Status Update from Guido”

  1. lambda lives! I still thought is was going 😀
    The __traceback__ in exceptions is a good move, even a bit of a “duh”.
    I’m only not sure about the point of identifiers with any unicode characters. Does this mean that some Chinese developers code write modules I need to import, where I can’t even distinguish (at first glance) different functions? Or did I misunderstand that?
    I hate it already when people use non-english identifiers, or even comments. And English is not my first language btw.

  2. Heh, personally I think that lambda will be around for a while, if for no other reason then to let people write examples that are shorter then those written in Perl!

    Well as far as the unicode stuff is concerned, the standard library will continue to use ASCII only, but it does mean that there could be certain modules that used unicode symbols for all of their identifiers. But I don’t think that it’s that big of a deal since people could already write modules with nonsensical ASCII identifier names!

    But we’ll have to way to see what happens with it!

Leave a Reply

Your email address will not be published. Required fields are marked *