On 4/18/07, Greg Ewing <[EMAIL PROTECTED]> wrote: > I'd rather see syntactic support for making a > normal inherited method call without danger of > using the wrong class, e.g. if you change a > base class but forget to update inherited calls > to match.
Could you give an example? My first three readings of this were (1) Huh? (2) You mean, if the __bases__ are changed, super doesn't get updated? (It does, as I just verified.) (3) You mean, with an explicit call, such as B.meth1(self), you want some sort of warning if class B changes the signature of meth1? (Presumably at compile-time; an incompatible change will already be caught at run-time.) -jJ _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
