3 ms·
If it were only syntax, 2to3 would be the answer. Exceptions and Print are not the problem. Migrating unicode-aware code and CPython extensions is a much bigger
by Derbasti 12y ago
If it were only syntax, 2to3 would be the answer. Exceptions and Print are not the problem. Migrating unicode-aware code and CPython extensions is a much bigger task, and incidentally, much more useful.
nonlocal, asyncio, unicode, yield from. If you ask me, these four are very compelling reasons to switch to Python 3 and they solve very real problems.
- overgard 12y agoThose 4 things are really just nice-to-have features though. I can work around all of those with minimal effort (asyncio and unicode), or it just doesn't come up much (yield from and nonlocal) To me, a compelling feature is a pypy like jit, or fixing the Gil, or lamdas that don't suck. For things like that, I'm willing to break the ecosystem. But for sorta better Unicode? Ha!
- kansface 12y agoThere are not so terrible workarounds for all the things you mentioned. While Py3K does them better, they are still not reasons to update. As the article points out, there isn't a compelling reason other than slightly cleaner code. The community agrees as evidenced by the massive push back.
- Derbasti 12y agoThere are not so terrible workarounds for things like functions or variables in assembler. While C does them better, they are not reasons to update. There are not so terrible workarounds for things like closures and memory management in C. While Python does them better, they are not reasons to update. There will always be neophiles and neophobes...