Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #4296 > unrolled thread

Re: Composition instead of inheritance

Started byIan Kelly <ian.g.kelly@gmail.com>
First post2011-04-28 22:23 -0600
Last post2011-04-28 22:23 -0600
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Composition instead of inheritance Ian Kelly <ian.g.kelly@gmail.com> - 2011-04-28 22:23 -0600

#4296 — Re: Composition instead of inheritance

FromIan Kelly <ian.g.kelly@gmail.com>
Date2011-04-28 22:23 -0600
SubjectRe: Composition instead of inheritance
Message-ID<mailman.983.1304051025.9059.python-list@python.org>
On Thu, Apr 28, 2011 at 11:15 AM, Ethan Furman <ethan@stoneleaf.us> wrote:
> For anybody interested in composition instead of multiple inheritance, I
> have posted this recipe on ActiveState (for python 2.6/7, not 3.x):
>
> http://code.activestate.com/recipes/577658-composition-of-classes-instead-of-multiple-inherit/
>
> Comments welcome!

On line 14, is it intentional that attributes whose values happen to
be false are not considered as conflicts?

On line 31, this code:

thing = getattr(thing, '__func__', None) or thing

could be simplified to this:

thing = getattr(thing, '__func__', thing)

Cheers,
Ian

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web