On Tue, Jun 21, 2016 at 3:21 PM, Nick Coghlan wrote:
> It occurs to me that a settable __definition_order__ provides a
> benefit that an ordered tp_dict doesn't: to get the "right" definition
> order in something like Cython or dynamic type creation, you don't
> need to carefully craft the order i
On 20 June 2016 at 19:11, Eric Snow wrote:
> FWIW, regarding repercussions, I do not expect any other potential
> future feature will subsume the functionality of PEP 520. The closest
> thing would be if cls.__dict__ became ordered. However, that would
> intersect with __definition_order__ only
On Mon, Jun 20, 2016 at 10:32 AM, Guido van Rossum wrote:
> - I don't like the exception for dunder names. I can see that __module__,
> __name__ etc. that occur in every class are distractions, but since you're
> adding methods, you should also add methods with dunder names like
> __init__ or __g
PEP 520 review notes.
(From previous message; edited.)
- I agree it's better to define the order as computed at runtime.
- I don't think there's much of a point to mandate that all
builtin/extension types reveal their order too -- I doubt there will be
many uses for that -- but I don't want to d
