Message201249
| 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 |
<CADiSq7e6BOV=jpteLD-bsDt+8TD340Lgda-CTjX_y7kyJt9ggA@mail.gmail.com> |
| In-reply-to |
<1382717852.2523.0.camel@fsol> |
| Content |
On 26 Oct 2013 02:18, "Antoine Pitrou" <report@bugs.python.org> wrote:
>
>
> Antoine Pitrou added the comment:
>
> > The problem we're trying to solve is CPython *silently* breaking
subclass
> > 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 <report@bugs.python.org>
> <http://bugs.python.org/issue10977>
> _______________________________________ |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年10月25日 16:23:05 | ncoghlan | set | recipients:
+ ncoghlan, rhettinger, pitrou, scoder, benjamin.peterson, eric.araujo, Arfrever, Trundle, skrah, meador.inge, daniel.urban, docs@python, eric.snow |
| 2013年10月25日 16:23:05 | ncoghlan | link | issue10977 messages |
| 2013年10月25日 16:23:05 | ncoghlan | create |
|