From: Jez Ng <re...@bu...> - 2012-06-16 11:21:02
|
New submission from Jez Ng <je...@gm...>: The test was originally created for issue 4920 in CPython, where MutableSet.pop was erroneously throwing an exception. The test introduced ended up checking the return value of pop() as well, probably to be on the safe side. However, since the underlying set() that implements MutableSet returns elements in an arbitrary order[1], checking for a specific return value means the test is implementation-dependent. I've changed it to check that the returned value is any one of the values that were initially put into the set. [1]: http://docs.python.org/library/stdtypes.html#set.pop ---------- files: set_pop messages: 7234 nosy: int3 severity: normal status: open title: Adjust MutableSet.pop test so we do not need to skip it Added file: http://bugs.jython.org/file1286/set_pop _______________________________________ Jython tracker <re...@bu...> <http://bugs.jython.org/issue1926> _______________________________________ |