This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Windson Yang
Recipients Windson Yang, docs@python, gvanrossum, njs, zach.ware
Date 2018-08-31.05:37:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535693872.67.0.56676864532.issue34552@psf.upfronthosting.co.za>
In-reply-to
Content
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__".
History
Date User Action Args
2018-08-31 05:37:52Windson Yangsetrecipients: + Windson Yang, gvanrossum, njs, docs@python, zach.ware
2018-08-31 05:37:52Windson Yangsetmessageid: <1535693872.67.0.56676864532.issue34552@psf.upfronthosting.co.za>
2018-08-31 05:37:52Windson Yanglinkissue34552 messages
2018-08-31 05:37:51Windson Yangcreate