Manuel,
How do you make sure that the pure Python part remains compatible with the
backend?
I'm thinking of selecting the versions explicitly in the front cppyy package:
it already has different dependencies selected based on interpreter: PyPy or
CPython. Also, the backend "API" is small and stable, so I expect a large
number of versions to work well, including older ones, moving forward.
If you have a better idea, then I'm all ears! I'm new to this packaging ...
Can we include the pure Python part in PyPy, in the way as it's done for
cffi?
Yes, albeit that it is still necessary to install cppyy_backend (contains a
patched version of Clang/LLVM), so I don't see much net gain.
And yes, it is technically possible to write a bindings generator that only
depends on LLVM during offline bindings generation, not at run-time. But
then you'd just have SWIG (albeit with a standards-compliant parser).
Best regards,
Wim
--
wlavrij...@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
