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 ezio.melotti
Recipients cvrebert, docs@python, ezio.melotti, mark.dickinson, rhettinger, terry.reedy
Date 2011-12-02.16:49:27
SpamBayes Score 2.61154e-07
Marked as misclassified No
Message-id <>
Would it be ok to state that:
1) <, >, ==, >=, <=, and != compare the values of two objects;
2) the two objects don't necessarily have to be of the same type;
3) with == and !=, objects of different types compare unequal, unless they define a specific __eq__ and/or __ne__;
4) with <, >, <=, and >=, the comparison of objects of different types raises a TypeError, unless they define specific __lt__, __gt__, __le__, and __ge__;
5) some built-in types define these operations, so it's possible to compare e.g. int and floats;

This should summarize the possible behaviors.  There's no reason IMHO to expose implementation details and to special case built-in types (unless their comparison is actually different and doesn't depend on __eq__, __ne__, etc.).
Date User Action Args
2011-12-02 16:49:28ezio.melottisetrecipients: + ezio.melotti, rhettinger, terry.reedy, mark.dickinson, cvrebert, docs@python
2011-12-02 16:49:28ezio.melottisetmessageid: <>
2011-12-02 16:49:27ezio.melottilinkissue12067 messages
2011-12-02 16:49:27ezio.melotticreate