[Python-ideas] Re: new PEP: implementation independent native code invocation and data exchange ABI standard (not sure if accurate)

On Sun, Apr 23, 2023, 3:43 PM turnbull wrote: > This isn't a PEP yet: it's a set of requirements. A PEP eventually > needs to > say how to implement the requirements, and even at this "proto-PEP" > stage, > it needs to be plausible that it's implementable. It's on you to > explain > how your

[Python-ideas] Re: new PEP: implementation independent native code invocation and data exchange ABI standard (not sure if accurate)

This isn't a PEP yet: it's a set of requirements. A PEP eventually needs to say how to implement the requirements, and even at this "proto-PEP" stage, it needs to be plausible that it's implementable. It's on you to explain how your very ambitious requirements can be satisfied in Python.

[Python-ideas] Re: new PEP: implementation independent native code invocation and data exchange ABI standard (not sure if accurate)

Thus is x very hard problem— bug people are trying. https://www.pypy.org/posts/2018/09/inside-cpyext-why-emulating-cpython-c-8083064623681286567.html -CHB On Sun, Apr 23, 2023 at 5:39 AM Jelle Zijlstra wrote: > At the Language Summit a few days ago we discussed this problem. I wasn't >

[Python-ideas] Re: new PEP: implementation independent native code invocation and data exchange ABI standard (not sure if accurate)

At the Language Summit a few days ago we discussed this problem. I wasn't involved in this discussion, but it's a hard one to solve. You may be interested in HPy (https://hpyproject.org/), which aims to provide what you are looking for. El dom, 23 abr 2023 a las 6:18, Evan Greenup via