This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.moore
Recipients doerwalter, ncoghlan, paul.moore, ryan.freckleton
Date 2009-02-05.13:20:00
SpamBayes Score 0.00057959044
Marked as misclassified No
Message-id <1233840004.54.0.796824957215.issue5135@psf.upfronthosting.co.za>
In-reply-to
Content
Very good point. Registering for the standard ABCs seems like an
important use case. Unfortunately, it seems to me that ABCs simply don't
provide that capability - is there a way, for a given class, of listing
all the ABCs it's registered under? Even if the order is arbitrary,
that's OK.

Without that, I fail to see how *any* generic function implementation
("simple" or not) could support ABCs. (Excluding obviously broken
approaches such as registration-order dependent overload resolution).

The problem is that ABCs are all about isinstance testing, where generic
functions are all about *avoiding* isinstance testing. (As a compromise,
you could have a base generic function that did isinstance testing for
the sequence ABC).
History
Date User Action Args
2009-02-05 13:20:04paul.mooresetrecipients: + paul.moore, doerwalter, ncoghlan, ryan.freckleton
2009-02-05 13:20:04paul.mooresetmessageid: <1233840004.54.0.796824957215.issue5135@psf.upfronthosting.co.za>
2009-02-05 13:20:02paul.moorelinkissue5135 messages
2009-02-05 13:20:01paul.moorecreate