Greg Ewing wrote: > 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?
The interpreter doesn't promise to call those slots with "self" first - self will be the second argument in the "rop" case. See binary_op1() in abstract.c for the gory details (I had to go look it up myself in order to rediscover how it worked). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
