Re:Explicit bootstrapping of pip in Python installations
by DasIch on Tuesday October 22, 2013 @11:14AM
(#6592429)
The standard library only gets new features when a minor or major Python release happens. That doesn't happen very often which slows down development of anything in the stdlib significantly to the point that packages in the stdlib effectively "die".
To some extent this is intentional because anything that requires more frequent changes is probably not stable enough for inclusion in the stdlib, in practice it does cause some unintentional issues for example rather lacking timezone support.
I'm just not understanding how it's OK that a standard acceptance of a Python package really means that it should go to the graveyard.