Re: [pypy-dev] PyCodeObject incompatibility

2022-02-15 Thread Carl Friedrich Bolz-Tereick
Hi Dmitry, I can only reiterate, we would need some information about what that library is actually for to give more useful information at this point. As Matti said, most of these APIs cannot be usefully implemented in PyPy. most jitted functions do not *have* a filled frame object at all in PyPy

Re: [pypy-dev] PyCodeObject incompatibility

2022-02-14 Thread Matti Picus
On 15/2/22 05:15, Dmitry Kovner wrote: Hi, again! First of all, thanks for the fast reply! The answer helped me a lot. However, during the porting of the extension to the awesome PyPy, I've got more questions: 1. The extension uses opcodes from cPython's opcode.h header file. (https://github.c

Re: [pypy-dev] PyCodeObject incompatibility

2022-02-14 Thread Dmitry Kovner
Hi, again! First of all, thanks for the fast reply! The answer helped me a lot. However, during the porting of the extension to the awesome PyPy, I've got more questions: 1. The extension uses opcodes from cPython's opcode.h header file. ( https://github.com/python/cpython/blob/8a84aef0123bd8c13cf8

Re: [pypy-dev] PyCodeObject incompatibility

2022-02-10 Thread Armin Rigo
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

Re: [pypy-dev] PyCodeObject incompatibility

2022-02-10 Thread Carl Friedrich Bolz-Tereick
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

Re: [pypy-dev] PyCodeObject incompatibility

2022-02-10 Thread Armin Rigo
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/

[pypy-dev] PyCodeObject incompatibility

2022-02-10 Thread Dmitry Kovner
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.