RichCompare and RichCompareBool

[Mark Dickinson]

On Mar 9, 3:22 pm, Aaron Brady <castiro... at gmail.com> wrote:
> My complaint was that the docs for the function, as well as its name,
> are misleading.  RichCompareBool should not take the short cut, and "x
> in [x]" should call something else that does.  (I am not arguing
> against the decided behavior of "x in [x]", btw.  There's no clear
> case IMO.)

I agree the docs are misleading.  A doc patch would very likely
be accepted.  Changing the behaviour or name of
PyObject_RichCompareBool would be trickier, since
that would risk breaking 3rd party extensions that depend
on the current behaviour.

Mark