[issue11388] Implement MutableSequence.clear()

Changes by Eli Bendersky : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue11388] Implement MutableSequence.clear()

Eli Bendersky added the comment: Documentation fix and some unit tests committed in revision 88742 -- ___ Python tracker ___ ___ Pyth

[issue11388] Implement MutableSequence.clear()

Raymond Hettinger added the comment: Please also update the table entry for MutableSequence in Doc/library/collections.abc.rst -- ___ Python tracker ___ ___

[issue11388] Implement MutableSequence.clear()

Georg Brandl added the comment: Creating a minimal concrete subclass and testing with that would be the obvious thing. -- ___ Python tracker ___ ___

[issue11388] Implement MutableSequence.clear()

Eli Bendersky added the comment: Committed in revision 88740 The non-abstract methods of MutableSequence and other classes currently seem to have no unit-tests. Any ideas about the best testing strategy for them? -- ___ Python tracker

[issue11388] Implement MutableSequence.clear()

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue11388] Implement MutableSequence.clear()

Georg Brandl added the comment: +1. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue11388] Implement MutableSequence.clear()

Raymond Hettinger added the comment: s/has to be/could be/ But yes, this would be a worthwhile addition to MutableSequence :-) -- nosy: +stutzbach ___ Python tracker ___ __

[issue11388] Implement MutableSequence.clear()

New submission from Eli Bendersky : Now that both list and bytearray support the clear() method (see issue #10516), MutableSequence.clear() has to be implemented. This is pending on commit for issue #11386, which fixes the exception thrown by bytearray.pop() when the bytearray is empty. -