Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Billy Mays Newsgroups: comp.lang.python Subject: Re: Updated blog post on how to use super() Date: Wed, 01 Jun 2011 09:03:42 -0400 Organization: Aioe.org NNTP Server Lines: 29 Message-ID: References: <80476fba-1b57-4bb1-9d7d-391edaf3042d@22g2000prx.googlegroups.com> NNTP-Posting-Host: 1EWTV5ij8IWwF9xB3mPhgA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.7) Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:6791 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