User: Password:
|
|
Subscribe / Log in / New account

Why move to Python 3?

Why move to Python 3?

Posted Nov 12, 2009 12:16 UTC (Thu) by jonth (subscriber, #4008)
Parent article: Python moratorium and the future of 2.x

I can only offer a personal perspective on the reasons the transition to Python 3 isn't happening quickly, but I think it's salient.

For work, I maintain a number of python scripts & modules, which were written when Python 2.4 was current. These scripts work on Python 2.5 and 2.6. They are not compatible with Python 3.0, and any changes to do so won't be backwards compatible with Python 2.x, so to support Python 3.0 I'll need to fork my code.

So, here's the obvious question. Why should I move? It's a significant amount of work to do it, requires that I maintain two different codebases and I get no benefit at all from updating to Python 3.0.


(Log in to post comments)

Why move to Python 3?

Posted Nov 14, 2009 16:07 UTC (Sat) by man_ls (guest, #15091) [Link]

Another perspective. I maintain a specialized Python package published under the GPL (recently accepted in Debian), and I want to maximize the number of people that can run it. This means keeping backward compatibility from Python 2.3, so I don't use any features added in 2.4, 2.5 or 2.6. I guess that most maintainers are in the same situation. So you can imagine my feelings about migrating to 3.x: no amount of flag days is going to help here. Frankly, I would rather migrate to Lua (an intriguing language that I want to learn anyway) than to Python 3.x, so if 2.x grows cobwebs I know what to do.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds