> I definitely must mention HPy, but yes, too early to recommend it for
> production purposes.
:D
> As for Cython/CFFI/ctypes, I keep having the intuition that CFFI can (and
> likely should) replace all uses of ctypes (I've never seen anything else in
> the stdlib cause as many Python hard cra
I definitely must *mention* HPy, but yes, too early to *recommend* it for
production purposes.
As for Cython/CFFI/ctypes, I keep having the intuition that CFFI can (and
likely should) replace all uses of ctypes (I've never seen anything else in
the stdlib cause as many Python hard crashes as ctype
On Thu, Jul 21, 2022 at 11:01 AM Phyo Arkar Lwin wrote:
> How about HPY : https://github.com/hpyproject/hpy I think it is the best
> route currently?
HPy is hopefully the future replacement for the C API itself, but it's
not something one can use in production *right now* so it's probably
not
How about HPY : https://github.com/hpyproject/hpy I think it is the best
route currently?
On Thu, Jul 21, 2022 at 6:39 AM Alex Martelli via pypy-dev <
pypy-dev@python.org> wrote:
> Hi Maciej, Armin, et al!
>
> Together with co-authors I've CC'd, I'm getting close to finishing the 4th
> edition
Hi Alex!
On Thu, 21 Jul 2022 at 02:08, Alex Martelli via pypy-dev
wrote:
> credible examples, esp. one setting CFFI head-to-head against ctypes (but
> comparisons with cython and the API would be fine too -- IF I could figure
> out how to define completely new Python types in CFFI, which so far
