Jesse Noller wrote:
On Sun, May 23, 2010 at 7:52 AM, Steve Holden <steve@holdenweb.com> wrote: ...snip...
Issues like the ones I'm bringing up could be fixed pretty straightforwardly if it were just a matter of filing a bug on a small package, but fixing a stdlib module is a major undertaking. True but I don't think that is a convincing argument. A subset of the functionality provided by this module is already available in Java and C++ and (at least in Java) it is used extensively and without too much trouble. If there are implementation bugs then we can fix them just like we would with any other module.
I don't see the availability of this functionality in those languages as any kind of reason why this needs to go into the stdlib now. Is there some desperate rush to get it in? If it were used extensively from PyPi *that* would be a recommendation ...
Not picking Steve's particular comments out - but Brian cites the previous discussions in the PEP itself:
http://www.python.org/dev/peps/pep-3148/
All of you questioning "Why should this be in the standard library" should go read those old threads, where that question was answered numerous times. Now I suddenly regret leaving the floodgates open, as we're rapidly rehashing discussions from months ago.
Yes, it might have been better to call for participation from those who had contributed to the original discussion, and therefore knew what they were talking about. No flood from me, though, all my questions have been answered. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 See Python Video! http://python.mirocommunity.org/ Holden Web LLC http://www.holdenweb.com/ UPCOMING EVENTS: http://holdenweb.eventbrite.com/ "All I want for my birthday is another birthday" - Ian Dury, 1942-2000