[Python-Dev] attributes of Python code objects

[Brett Cannon]

On Sun, 26 Feb 2017 at 02:20 Xavier de Gaye <xdegaye at gmail.com> wrote:

> In PR 218 [1], INADA Naoki wrote:
>  > I think attributes of Python's code object is implementation detail,
> even
>  > though PyPy follows.
>  > But it's not big problem until there are some Python implementation
>  > having different code implementation.
>
> Python's code object attributes are described in the Data Model [2]
> section of
> the documentation.  1) Is this description normative (to be followed by
> all the
> implementations of the Python language)?  2) Is the description of
> co_lnotab
> in [3] normative ?
>

That's a good question. "Code objects represent byte-compiled executable
Python code, or bytecode" which would suggest that if an implementation
didn't have a compiled code then code objects wouldn't make sense. Then
again the object contains details about the function that can be useful and
are relied upon by parts of the stdlib (e.g. inspect.signature() can't
function without the code object).

Due to that last point I would say the attributes on code objects are not
an implementation detail, but it's acceptable for things like co_code to be
set to None when it doesn't make sense.

-Brett


>
> Xavier
>
> [1] https://github.com/python/cpython/pull/218
> [2] https://docs.python.org/3/reference/datamodel.html
> [3] https://github.com/python/cpython/blob/master/Objects/lnotab_notes.txt
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brett%40python.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20170226/020dd3be/attachment.html>