Author ncoghlan
Recipients alex, barry, docs@python, eric.snow, ethan.furman, mark.dickinson, ncoghlan, serhiy.storchaka, vstinner
Date 2013-08-04.11:29:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375615765.09.0.934256182267.issue17576@psf.upfronthosting.co.za>
In-reply-to
Content
The deprecation warning version looks good to me.

Something I'll mention explicitly (regarding the PyCon discussions that Eric mentioned above), is that we unfortunately couldn't do something like this for the various concrete APIs with overly permissive subclass checks. For those APIs, calling them directly was often the *right* thing for simple subtypes implemented in C to use to call up to the parent implementation.

This case is different, as it's the *abstract* APIs that currently have the overly permissive checks.
History
Date User Action Args
2013-08-04 11:29:25ncoghlansetrecipients: + ncoghlan, barry, mark.dickinson, vstinner, alex, docs@python, ethan.furman, eric.snow, serhiy.storchaka
2013-08-04 11:29:25ncoghlansetmessageid: <1375615765.09.0.934256182267.issue17576@psf.upfronthosting.co.za>
2013-08-04 11:29:25ncoghlanlinkissue17576 messages
2013-08-04 11:29:24ncoghlancreate