Python 2 to 3 conversion - embrace the pain

[Paul Rubin]

Steven D'Aprano <steve+comp.lang.python at pearwood.info> writes:
> 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. 

I always thought twisted and zope were monstrosities.  I've used threads
instead of twisted and various other possibilities instead of zope.  Not
sure why numpy couldn't go in the stdlib: does it change all that fast?
PLY is an application not a library.  

> 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.

Has that been a problem for PHP?