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 ncoghlan
Recipients Arfrever, Trundle, benjamin.peterson, daniel.urban, docs@python, eric.araujo, eric.snow, meador.inge, ncoghlan, pitrou, rhettinger, scoder, skrah
Date 2013-10-25.16:23:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <1382717852.2523.0.camel@fsol>
On 26 Oct 2013 02:18, "Antoine Pitrou" <> wrote:
> Antoine Pitrou added the comment:
> > The problem we're trying to solve is CPython *silently* breaking
> > invariants, which is what the concrete APIs currently do.
> To be clear: the problem is with CPython calling the concrete APIs when
> it shouldn't, rather than with the concrete APIs not behaving properly.

The boilerplate required to use them correctly renders them broken in my
view, particularly when they silently corrupt internal subclass state when
misused instead of throwing an exception.

> ----------
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2013-10-25 16:23:05ncoghlansetrecipients: + ncoghlan, rhettinger, pitrou, scoder, benjamin.peterson, eric.araujo, Arfrever, Trundle, skrah, meador.inge, daniel.urban, docs@python, eric.snow
2013-10-25 16:23:05ncoghlanlinkissue10977 messages
2013-10-25 16:23:05ncoghlancreate