New submission from Windson Yang <wiwind...@gmail.com>:
In https://docs.python.org/3.5/library/stdtypes.html#comparisons "some types (for example, function objects) support only a degenerate notion of comparison where any two objects of that type are unequal." We had some discussion at zulipchat already: "more seriously: I think we can just delete that sentence. The next sentence makes clear that < and friends arne't always defined, and the sentence after that notes that == defaults to is if there's nothing better." - by Nathaniel J. Smith IMO, I think we should also clarify the relationship between "==", "is" and "__eq__". ---------- assignee: docs@python components: Documentation messages: 324403 nosy: Windson Yang, docs@python, gvanrossum, njs, zach.ware priority: normal severity: normal status: open title: Clarify built-in types comparisons type: enhancement versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34552> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
