[issue28785] Clarify the behavior of NotImplemented
Max
report at bugs.python.org
Thu Nov 24 05:38:11 EST 2016
Max added the comment:
Martin - what you suggest is precisely what I had in mind (but didn't phrase it as well):
> to document the above sort of behaviour as being directly associated with operations like as == and !=, and only indirectly associated with the NotImplemented object and the __eq__() method
Also a minor typo: you meant "If that call returns NotImplemented, the first fallback is to try the *reverse* call."
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28785>
_______________________________________
More information about the Python-bugs-list
mailing list