[Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
Nick Coghlan
ncoghlan at gmail.com
Wed Aug 31 00:14:49 EDT 2016
More information about the Python-Dev mailing list
Wed Aug 31 00:14:49 EDT 2016
- Previous message (by thread): [Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
- Next message (by thread): [Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 31 August 2016 at 07:11, Chris Angelico <rosuav at gmail.com> wrote: > Didn't all this kind of thing come up when function annotations were > discussed? Insane schemes like dictionaries with UUID keys and so on. > The decision then was YAGNI. The decision now, IMO, should be the > same. Keep things simple. Different use case - for annotations, the *reader* of the code is one of the intended audiences, so as the author of the code, you decide what you want to tell them, and that then constrains the tools you can use (or vice-versa - you pick the kinds of tools you want to use, and that constrains what you can tell your readers). This case is different - there are no human readers involved, only automated tools, so adding a mandatory redirection through a sequence is just a small performance hit rather than a readability problem. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
- Next message (by thread): [Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list