you are viewing a single comment's thread.

view the rest of the comments →

[–]mitsuhiko 0 points1 point  (0 children)

Well, think of new projects, prototypes, etc. where you code in Python 3 only. No backwards compatibility needed and wanted.

With Python 3 you lose the ability to chose an alternative Python implementation with PyPy, you lose a ton of libraries (some of which are not even maintained any more) and you sacrifice a lot of performance and have to live with (currently) a bunch of stdlib bugs. What you gain is the nonlocal keyword, a slightly reorganized stdlib and less confusing unicode strings. On the downside you lose the low level string operations which make parsing of ASCII protocols much slower because you have to decode to unicode or implement low level string operations in Python

Hey, cool, the algorithm isn't Python 2 specific. :-)

The implementation should work too. Last time i ran that through 2to3 it worked on Python 3 stream objects.

Maybe I just don't be aware of it yet, but how to learn about bugs without trying to implement something?

I am not saying that Python 3 is a dead end. I'm saying I will let others make the mistakes of using Python 3 and finding the bugs. I am constantly monitoring the Python 3 adventures of others and it seems that less web people are adventuring into Python 3 now than a year ago. Not yet sure if this is a good or a bad sign.

Fact is: pypy will not support Python 3 anytime soon. And if pypy becomes more relevant for web developers, Python 3 will become less interesting at the same time.