[Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
Greg Ewing
greg.ewing at canterbury.ac.nz
Wed Sep 23 06:27:21 CEST 2009
More information about the Python-Dev mailing list
Wed Sep 23 06:27:21 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 ]
Willem Broekema wrote: > The AND above (which I uppercased) is subtle but important. In the "x > op y" case with y being of a subclass of the class of x, if there is > no class in between x and y (excluding x, including y) that overrides > the __rop__ method, then y,__rop__(x) is *not* tried before > x.__op__(y). How does this work at the C typeslot level, where there are no __rop__ methods? -- 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