On Sat, 10 Jul 2021, Dan Stromberg wrote:
On Sat, Jul 10, 2021 at 7:18 AM Roland Lutz wrote:
I've been moving the extensions from the CPython API to PyPy/CFFI
CFFI is probably good, but did you evaluate HPY?
HPy looks like it may be exactly what I've been looking for, but
unfortunately, acco
On Sat, 10 Jul 2021, Matti Picus wrote:
The canonical way is to use sysconfig
pypy -c "import sysconfig;print(sysconfig.get_config_var('EXT_SUFFIX'))"
.pypy37-pp73-x86_64-linux-gnu.so
On python2.7 use 'SO'
~/oss/pypy2.7-HEAD/bin/pypy -c "import
sysconfig;print(sysconfig.get_config_var('SO')
On 10/7/21 4:44 pm, Roland Lutz wrote:
How do I determine the correct filename extension for PyPy extension
modules?
The canonical way is to use sysconfig
pypy -c "import sysconfig;print(sysconfig.get_config_var('EXT_SUFFIX'))"
.pypy37-pp73-x86_64-linux-gnu.so
On python2.7 use 'SO'
~/
On Sat, Jul 10, 2021 at 7:18 AM Roland Lutz wrote:
> Hi,
>
Hi.
I am currently using CPython 2 extensions and code in a project that's
> mostly written in C. I've been moving the extensions from the CPython API
> to PyPy/CFFI;
CFFI is probably good, but did you evaluate HPY?
In order to build
Hi,
I am currently using CPython 2 extensions and code in a project that's
mostly written in C. I've been moving the extensions from the CPython API
to PyPy/CFFI; but now I'm struggling with integrating the CFFI extensions
into the Autotools build process.
With CPython, there is the autocon
