Author: brett.cannon Date: Thu Aug 24 03:13:18 2006 New Revision: 51534 Modified: peps/trunk/pep-3100.txt Log: Clarify why operator.isCallable() and operator.sequenceIncludes() are going away. Modified: peps/trunk/pep-3100.txt ============================================================================== --- peps/trunk/pep-3100.txt (original) +++ peps/trunk/pep-3100.txt Thu Aug 24 03:13:18 2006 @@ -209,7 +209,10 @@ not thread-safe; use ``sys.exc_info()`` or an attribute of the exception [2]_ [13]_ [#sys-module]_ * ``array.read``, ``array.write`` [#array-module]_ -* ``operator.isCallable``, ``operator.sequenceIncludes`` [#operator-module]_ +* ``operator.isCallable`` : ``callable()`` built-in is being removed + [#operator-module]_ +* ``operator.sequenceIncludes`` : redundant thanks to + ``operator.contains`` [#operator-module]_ * In the thread module, the aquire_lock() and release_lock() aliases for the acquire() and release() methods on lock objects. (Probably also just remove the thread module as a public API,