[Python-Dev] Update on PEP 523 and adding a co_extra field to code objects
Terry Reedy
tjreedy at udel.edu
Mon Aug 29 20:05:40 EDT 2016
On 8/29/2016 5:38 PM, Brett Cannon wrote:
> who objected to the new field did either for memory ("it adds another
> pointer to the struct that won't be typically used"), or for conceptual
> reasons ("the code object is immutable and you're proposing a mutable
> field"). The latter is addressed by not exposing the field in Python and
Am I correct is thinking that you will also not add the new field as an
argument to PyCode_New?
> clearly stating that code should never expect the field to be filled.
I interpret this as "The only code that should access the field should
be code that put something there."
--
Terry Jan Reedy
More information about the Python-Dev
mailing list