Hi,
On Thu, 10 Feb 2022 at 14:20, Carl Friedrich Bolz-Tereick wrote:
> are doing with them? But yes, as Armin write, accessing the the .co_*
> attributes with PyObject_GetAttrString is an approach!
Oops, sorry. Python 3 renamed various attributes to use the
double-underscore convention, like on
Hi Dmitry,
those fields are quite implementation-dependant, it's not clear to me
that their use can be just carried over from CPython in all cases. Could
you maybe tell us which exception module uses them or at least what you
are doing with them? But yes, as Armin write, accessing the the .co_*
a
Hi,
On Thu, 10 Feb 2022 at 14:03, Dmitry Kovner wrote:
> Hello! I'm trying to build a low-level C API extension of cPython to be used
> in PyPy. The extension extensively uses some fields of PyCodeObject
> (https://github.com/python/cpython/blob/f87e616af038ee8963185e11b96841c81e8ef15a/Include/
Hello! I'm trying to build a low-level C API extension of cPython to be
used in PyPy. The extension extensively uses some fields of PyCodeObject (
https://github.com/python/cpython/blob/f87e616af038ee8963185e11b96841c81e8ef15a/Include/code.h#L23):
co_firstlineno, co_stacksize, co_consts
and so on.
