homepage

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 rhettinger
Recipients Jim.Jewett, docs@python, ezio.melotti, martin.panter, r.david.murray, rhettinger
Date 2015年07月24日.01:38:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437701933.93.0.896957354256.issue22000@psf.upfronthosting.co.za>
In-reply-to
Content
> Why do we need a dedicated section in Built-in Types about Comparisons?
It is nice to have some of that information collected together. I think people learn about comparison logic as a single topic rather than piecemeal type by type.
To Jim's point, the discussion of "is" and "is not" should probably be factored-out (their meaning is type-invariant and is not overridable with a dunder method). Also, they don't have the same reflective logic as the rich comparisons.
History
Date User Action Args
2015年07月24日 01:38:54rhettingersetrecipients: + rhettinger, ezio.melotti, r.david.murray, docs@python, martin.panter, Jim.Jewett
2015年07月24日 01:38:53rhettingersetmessageid: <1437701933.93.0.896957354256.issue22000@psf.upfronthosting.co.za>
2015年07月24日 01:38:53rhettingerlinkissue22000 messages
2015年07月24日 01:38:53rhettingercreate

AltStyle によって変換されたページ (->オリジナル) /