Will Python 3.x ever become the actual standard?

[Steven D'Aprano]

On Wed, 23 Oct 2013 22:12:57 -0700, Peter Cacioppi wrote:

> I said
> 
> "Even Bill F*ng Gates was reluctant to break back compatibility,"

Don't be fooled though, Python is *extremely* reluctant to break 
backwards compatibility too. That's why Python has the "__future__" 
directive, and why some warts have ended up enshrined in the language.

For example, although string exceptions were recognised as a bad idea for 
many years, there was a long deprecation process to get rid of them. It 
took at least 11 years to remove them completely:

http://python-history.blogspot.com.au/2009/03/how-exceptions-came-to-be-classes.html

Nick Coglan describes some of the completing pressures on a language like 
Python:

http://www.boredomandlaziness.org/2011/04/musings-on-culture-of-python-dev.html


Because of the tension between users demanding Python change more 
quickly, and those demanding it changes more slowly, you can't satisfy 
everyone. You probably can't even satisfy anyone.


-- 
Steven