Message348068
I feel like I agree with Paul here, unsurprising behavior from ANY is it matching anything, with no expectation that third party objects have to correctly have a return path for NotImplemented on their __eq__ method. ANY doesn't currently do that.
I've added a commit with couple other failing tests showing how using assertEqual is currently order sensitive when used with _Call or _CallList objects. I've got a work in progress fixing all three tests that just needs a little clean up, but think I might be able to lessen the complexity of it by adding Paul's idea of just special casing ANY directly, which may be smaller than the fix I have.
Thank you all for providing such great feedback so far, this is really interesting stuff to me, and a great first time submitting to Python experience so far. |
|
Date |
User |
Action |
Args |
2019-07-17 15:50:53 | ElizabethU | set | recipients:
+ ElizabethU, serhiy.storchaka, p-ganssle, xtreak |
2019-07-17 15:50:53 | ElizabethU | set | messageid: <1563378653.55.0.188131474234.issue37555@roundup.psfhosted.org> |
2019-07-17 15:50:53 | ElizabethU | link | issue37555 messages |
2019-07-17 15:50:53 | ElizabethU | create | |
|