Greg Ewing greg.ewing at canterbury.ac.nz
Thu Sep 24 02:34:40 CEST 2009

• Previous message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
• Next message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Chris Withers wrote:

> But this isn't coercion! :-)

The raisin is probably hysterical. Once upon a time, Python
had a __coerce__ special method that took care of things
like this in a different (and inferior) way. It gradually
got replaced by the current scheme, but nobody changed the
section heading in the docs.

-- 
Greg

---

• Previous message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
• Next message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list