[Python-3000] Traits/roles instead of ABCs

BJörn Lindqvist bjourne at gmail.com
Tue May 1 00:01:37 CEST 2007

On 4/30/07, Bill Janssen <janssen at parc.com> wrote:
> > On 4/30/07, Raymond Hettinger <python at rcn.com> wrote:
> > > I'm concerned that the current ABC proposal will quickly evolve from optional
> > > to required and create somewhat somewhat java-esque landscape where
> > > inheritance and full-specification are the order of the day.
> >
> > +1 for preferring simple solutions to complex ones
> Me, too.  But which is the simple solution?  I tend to think ABCs are.

Neither or. They are both an order of a magnitude more complex than
the problem they are designed to solve. Raymond Hettingers small list
of three example problems earlier in the thread, is the most concrete
description of what the problem really is all about. And I would
honestly rather sort them under "minor annoyances" than "really
critical stuff, needs to be fixed asap."

One really wise person wrote a long while ago (I'm paraphrasing) that
each new feature should have to prove itself against the standard
library. That is, a diff should be produced proving that real world
Python code reads better with the proposed feature than without. If no
such diff can be created, the feature probably isn't that useful.

mvh Björn

More information about the Python-3000 mailing list