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 jyasskin
Recipients casevh, jyasskin, mark.dickinson
Date 2009-07-16.20:36:42
SpamBayes Score 7.613026e-08
Marked as misclassified No
Message-id <>
The fallback behavior in Fraction was meant to demonstrate the suggested 
fallback behavior for user-defined types. In particular, the idea was 
that all Reals would (by default) be comparable to each other, even if 
they didn't know about each other. Unfortunately, the comparison protocol 
provides no way to know if a particular call is the first call or the 
fallback, so __eq__(Fraction, b) has to return the same thing as 
__eq__(b, Fraction). If b doesn't know about Fraction, and Fraction wants 
to make a best attempt at comparing to it, then __eq__(Fraction, b) can't 
return NotImplemented.
Date User Action Args
2009-07-16 20:36:44jyasskinsetrecipients: + jyasskin, mark.dickinson, casevh
2009-07-16 20:36:44jyasskinsetmessageid: <>
2009-07-16 20:36:43jyasskinlinkissue6431 messages
2009-07-16 20:36:42jyasskincreate