On 4/24/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I'm not sure what the point would be of supporting dynamically
> modifying ABCs -- it looks like you're just exploring the corners of
> the semantics rather than providing actual use cases.
Yep, I'm just checking the corner case semantics.
On 4/24/07, Steven Bethard <[EMAIL PROTECTED]> wrote:
> On 4/24/07, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> > Or could __abstractmethods__ be created dynamically? Which would be
> > used less, __abstractmethods__ or setting class attributes, that it
> > would be OK to be a bit slower?
>
> I co
On 4/24/07, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> Or could __abstractmethods__ be created dynamically? Which would be
> used less, __abstractmethods__ or setting class attributes, that it
> would be OK to be a bit slower?
I considered that, but __abstractmethods__ gets checked at every clas
On 4/24/07, Steven Bethard <[EMAIL PROTECTED]> wrote:
> On 4/24/07, guido.van.rossum <[EMAIL PROTECTED]> wrote:
> > +We define a new built-in decorator, [EMAIL PROTECTED]
> [snip]
> > +**Implementation:** The [EMAIL PROTECTED] decorator sets the
> > +function attribute ``__isabstractmethod__`` to t
On 4/24/07, guido.van.rossum <[EMAIL PROTECTED]> wrote:
> +We define a new built-in decorator, [EMAIL PROTECTED]
[snip]
> +**Implementation:** The [EMAIL PROTECTED] decorator sets the
> +function attribute ``__isabstractmethod__`` to the value ``True``.
> +The ``type.__new__`` method computes the t
