On Tue, Jan 09, 2007, Brett Cannon wrote: > On 1/9/07, Collin Winter <[EMAIL PROTECTED]> wrote: >> On 1/5/07, Brett Cannon <[EMAIL PROTECTED]> wrote: >>> Obsolete >>> -------- >>> >>> Becoming obsolete signifies that either another module in the stdlib >>> or a widely distributed third-party library provides a better solution >>> for what the module is meant for. >> >> How about the sets module? The set and frozenset types would seem to >> have made a separate module obsolete. >> >> I've just refreshed SF patch #1500611, which removes all usages of the >> sets module from the stdlib and test suite. > > Well, I have no issue removing it, but I know some people really like > having the Python version of the built-ins around (e.g., User*). Plus > I don't know if PyPy or IronPython use it for their set > implementation. > > What do other people think?
I'm generally a fan of providing Python versions of C modules. It makes Python more accesible to someone ramping up. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "Plus ca change, plus c'est la meme chose." _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
