With Perl, there's a dozen solutions on CPAN for every problem, and you can pick and choose to find the best one. In Python, there's usually one that's had the blessing from above, and like-it-or-lump-it, that's the one everyone's using.
I think you have a misconception about Python.
The equivalent to CPAN in the Python world is not the std library but PyPI (easy_install).
Zed's whining is inappropiate, he should just get to work. The current recommended practice to get something into the stdlib is:
1. Build it as an external package.
2. If it's good people will use it, it becomes popular, bugs get fixed.
3. Eventually it enters the stdlib (potentially obsoleting whatever package previously did the task)
Yes, the stdlib has accumulated a lot of cruft over the years due to the higher ups not adhering to this procedure. That's only more reason to tighten the criteria and accept new stuff only when it has proven itself in the wild - and not because a particular name is printed on it (be it Zed or someone else's).
I think you have a misconception about Python. The equivalent to CPAN in the Python world is not the std library but PyPI (easy_install).
Zed's whining is inappropiate, he should just get to work. The current recommended practice to get something into the stdlib is:
1. Build it as an external package.
2. If it's good people will use it, it becomes popular, bugs get fixed.
3. Eventually it enters the stdlib (potentially obsoleting whatever package previously did the task)
Yes, the stdlib has accumulated a lot of cruft over the years due to the higher ups not adhering to this procedure. That's only more reason to tighten the criteria and accept new stuff only when it has proven itself in the wild - and not because a particular name is printed on it (be it Zed or someone else's).