Python 2 to 3 conversion - embrace the pain

Mon Mar 16 04:00:37 EDT 2015

On Monday 16 March 2015 17:17, Paul Rubin wrote:

> Chris Angelico <rosuav at gmail.com> writes:
>> Ah but it isn't Py3 that's all about being first - it's the latest
>> version of some third-party module.
> 
> You know, one of the attractions of Python used to be that it came with
> a powerful enough standard library that you didn't really need third
> party modules very often.

The std lib is *batteries* included. If you need a nuclear reactor, you turn 
to third-party frameworks and libraries like Twisted, Zope, numpy, PLY, etc. 
They would be a bad fit in the standard library. It has been said that the 
stdlib is the place good code goes to die.

It's precisely because the stdlib has much stronger backward compatibility 
requirements and a higher reluctance to break things that fast-changing 
projects (including just bug fixes, not just new features) cannot go into 
the stdlib.

-- 
Steve