r/Python • • May 27 '14

Python 3 is fine | Sealed Abstract

http://sealedabstract.com/rants/python-3-is-fine/
234 Upvotes

96 comments sorted by

View all comments

28

u/ThePurpleAlien May 28 '14

I'm glad this was posted in response to "python 3 is killing python". We've just decided to move our simulation software to Python 3 and the previous article had me a bit worried about Python's fate. So it's good to hear a robust defense of Python 3, but there's also a bit of attitude in this post that I don't like: the idea that Python 3 is just the product of a bunch of volunteers coders having fun, why should they care about you and your problems with Python 2/3? You do what you want to do (including forking Python 2 if that floats your boat); let the Python devs do whatever floats their boat.

But this attitude is actually not ok. Python is not just a fun experiment; it is a successful language as the Python.org website is eager to illustrate in the "Success Stories" section. Many businesses depend on it, a lot of money and innovation rides on it. And evidently, the python community thinks that's a good thing, it's maybe even a bit smug about it. So it's not acceptable to say that Python's devs can just hack away in a bubble of self interest. While Python 3 is hopefully not actually killing Python, ignoring the concerns of everyday Python users will kill Python. According to this author, that's ok because the Python devs are just volunteers having fun. But I don't think those devs would say that's ok. Python's success is a big part of what makes all their work relevant. So even if resistance to Python 3 is misguided, it is somewhat pervasive, and the Python community ought to have a good (i.e. not merely dismissive and patronizing) answer to those concerns.

12

u/shadowmint May 28 '14

yep; this /r/circlejerk approach to the issue (oh, I work in python 3, and so do all my friends, its great!) is really the problem.

I think its particularly telling that Guido himself works primarily in python 2 at Dropbox, and unsurprisingly we now have support for the 2.7 line in security patches to 2020. At least a few of the core developers must be awake.

The OP raises a valid point. It is an open source project. If you want change, you have to actually get involved, not just complain.

...that said, is encouraging the complainers to fork and start 2.8 really a good idea? (no, it's not; its a flat out terrible idea. It'll divide the community even more). Making python 3 compellingly better than the 2.x line is really the path forward.

4

u/[deleted] May 28 '14

that said, is encouraging the complainers to fork and start 2.8 really a good idea?

He is not actually encouraging them. The "Python 3 is killing Python" is. This response is just saying "If that's such a great idea, why don't you do it?"

The fact is that this has been discussed many times before. In January there was an actual call for this, and an IRC channel was created. Nobody have posted in it since January, despite the channel having several people claiming that a Python 2.8 fork should happen.

That's his point. He is not encouraging it, he said that if it was such a great idea it would have happened by now.

(The main problem with 2.8 is of course that nobody knows what should go in it).