Skip to content
This repository was archived by the owner on Nov 23, 2017. It is now read-only.
This repository was archived by the owner on Nov 23, 2017. It is now read-only.

Avoid using subclassing as an API #19

Open
@GoogleCodeExporter

Description

@GoogleCodeExporter
There's been some good talk at PyCon about the danger of using subclassing as 
an API style, and recommending composition of objects instead.  We should 
review all our APIs to see if we're in danger of falling in this trap.  It is 
one of the reasons asyncore is such a disaster.

Original issue reported on code.google.com by gvanrossum@gmail.com on 21 Mar 2013 at 3:50

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions