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 <rep...@bugs.python.org> <http://bugs.python.org/issue28785> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
