PyPy Support via cpyext - What's needed?

[omerbenamram]

Hi,
I've been messing around with pyo3 and have been really enjoying it - the simplicity is fantastic, and it seems overhead with cpython is minimal, and very pleasant to work with.
Our production parsing systems run PyPy for the massive speedup gains we get for some text parsing cases we have implemented in python.
From my benchmarks, implementing identical parsers in rust yield around 250x~ time the speed of cpython, and around 15x that of pypy.

However for gradual migration we'd probably want to be able to load the rust extensions side-by-side with out running pypy processes.

It does seem that PyO3 recognizes pypy to some degree, as I did get two seperate shared libs

I've tried fiddling a little bit with PyO3 building code (on mac), but wasn't able to make anything meaningful so far 😕

Do you think it would be a big undertaking to make PyO3 compatible with cpyext? if so, what would be needed to make this work?

Thanks alot!

[fafhrd91]

When I actively worked on pyo3 I looked to a cpyext compatibility. But decided against it because cpyext integration is super slow. Cffi integration with pypy is much faster. Personally I don’t have time to do any integration work. But I’ll accept PRs for sure.

To integrate with pypy you need 2 changes:

1. Add pypy detection to build.rs (easy)
2. Modify pyo3::ffi3 and limit exportable api

[fafhrd91]

please reopen, if you have more questions