[issue11388] Implement MutableSequence.clear()
Changes by Eli Bendersky eli...@gmail.com: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: Please also update the table entry for MutableSequence in Doc/library/collections.abc.rst -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
Eli Bendersky eli...@gmail.com added the comment: Documentation fix and some unit tests committed in revision 88742 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
New submission from Eli Bendersky eli...@gmail.com: 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. -- assignee: eli.bendersky components: Library (Lib) keywords: easy messages: 129994 nosy: eli.bendersky, georg.brandl, ncoghlan, rhettinger, terry.reedy priority: normal severity: normal stage: needs patch status: open title: Implement MutableSequence.clear() type: behavior versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
Raymond Hettinger rhettin...@users.sourceforge.net added the comment: s/has to be/could be/ But yes, this would be a worthwhile addition to MutableSequence :-) -- nosy: +stutzbach ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
Georg Brandl ge...@python.org added the comment: +1. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
Changes by Daniel Urban urban.dani...@gmail.com: -- nosy: +durban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
Eli Bendersky eli...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11388] Implement MutableSequence.clear()
Georg Brandl ge...@python.org added the comment: Creating a minimal concrete subclass and testing with that would be the obvious thing. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
