[docs] [issue34552] Clarify built-in types comparisons
report at bugs.python.org
Fri Aug 31 01:37:52 EDT 2018
New submission from Windson Yang <wiwindson at gmail.com>:
"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 at python
nosy: Windson Yang, docs at python, gvanrossum, njs, zach.ware
title: Clarify built-in types comparisons
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8
Python tracker <report at bugs.python.org>
More information about the docs