On 5/31/2011 10:44 PM, Raymond Hettinger wrote:
I've tightened the wording a bit, made much better use of keyword
arguments instead of kwds.pop(arg), and added a section on defensive
programming (protecting a subclass from inadvertently missing an MRO
requirement). Also, there is an entry on how to use assertions to
validate search order requirements and make them explicit.
http://bit.ly/py_super
or
http://rhettinger.wordpress.com/2011/05/26/super-considered-super/
Any further suggestions are welcome. I'm expecting this to evolve
into how-to guide to be included in the regular Python standard
documentation. The goal is to serve as a reliable guide to using
super and how to design cooperative classes in a way that lets
subclasses compose and extent them.
Raymond Hettinger
--------
follow my python tips on twitter: @raymondh
I read this when it was on HN the other day, but I still don't see what
is special about super(). It seems (from your post) to just be a stand
in for the super class name? Is there something special I missed?
--
Bill
--
http://mail.python.org/mailman/listinfo/python-list
