[Python-Dev] PEP 520: Preserving Class Attribute Definition Order (round 5)
Guido van Rossum
guido at python.org
Tue Jun 28 16:55:56 EDT 2016
More information about the Python-Dev mailing list
Tue Jun 28 16:55:56 EDT 2016
- Previous message (by thread): [Python-Dev] PEP 520: Preserving Class Attribute Definition Order (round 5)
- Next message (by thread): [Python-Dev] PEP 520: Preserving Class Attribute Definition Order (round 5)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Awesome. That addresses my last concerns. PEP 520 is now accepted. Congratulations! On Tue, Jun 28, 2016 at 1:43 PM, Eric Snow <ericsnowcurrently at gmail.com> wrote: > On Tue, Jun 28, 2016 at 11:43 AM, Guido van Rossum <guido at python.org> wrote: >> On Tue, Jun 28, 2016 at 10:30 AM, Eric Snow <ericsnowcurrently at gmail.com> wrote: >>> I suppose I'm having a hard time letting go of the attractiveness of >>> "read-only == complete". However, given that you've been pretty clear >>> what you think, I'm more at ease about it. :) >> >> Yeah, it's time to drop it. ;-) > > Thanks for the feedback. I've updated the PEP to resolve the open > questions. Most notably, I've dropped the read-only constraint on the > __definition_order__ attribute. Please let me know if you have any > other outstanding concerns. Otherwise I think this PEP is ready for > pronouncement. :) > > -eric -- --Guido van Rossum (python.org/~guido)
- Previous message (by thread): [Python-Dev] PEP 520: Preserving Class Attribute Definition Order (round 5)
- Next message (by thread): [Python-Dev] PEP 520: Preserving Class Attribute Definition Order (round 5)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list