Python 3 might be fine, but I see no compelling reason to commit time and effort into moving to it. Sure, it has plenty of "exciting" features, but I'm a professional developer who writes boring code meant to last for years, if not decades. "Exciting" new features look fragile and unproven to me.
The OSes I develop for (and on) have Python 2 distributed with them, and provide hundreds of pre-compiled packages for them. Going through the effort of compiling my own packages and having to fight against the OS' version of Python just for a few new language features sounds like tilting at windmills to me.
As we're fond of saying in defense of our language... Python is good enough. I'll take that and extend it a bit: Python 2 is good enough for now.
"Exciting" new features look fragile and unproven to me.
If Python 3's features are "unproven" (maybe other than asyncio) to you, you better not release any code until millions of people have used it rigorously for five years.
3
u/[deleted] May 28 '14
Python 3 might be fine, but I see no compelling reason to commit time and effort into moving to it. Sure, it has plenty of "exciting" features, but I'm a professional developer who writes boring code meant to last for years, if not decades. "Exciting" new features look fragile and unproven to me.
The OSes I develop for (and on) have Python 2 distributed with them, and provide hundreds of pre-compiled packages for them. Going through the effort of compiling my own packages and having to fight against the OS' version of Python just for a few new language features sounds like tilting at windmills to me.
As we're fond of saying in defense of our language... Python is good enough. I'll take that and extend it a bit: Python 2 is good enough for now.