Is PyPy ideally plug'n'play, i.e. is it supposed to be able to seamlessly replace the CPython interpreter (ideally in that it may not factually be completely compatible, but is it aimed to be completely compatible)?
No. There's a documented list of things that are different. [0] That said, you likely don't have many of these issues in your code, if any. The ideal is for folks who write portable pure Python without relying on implementation-specific details to be able to run on PyPy and CPython without any hacks.
basically yes, with caveats, the big gotcha is C libraries exposed to python. CFFI helps alleviate this issue, but it's not a 100% identical replacement for the c bindings that CPython gives you. See their website for all the details.
Comments
Is PyPy ideally plug'n'play, i.e. is it supposed to be able to seamlessly replace the CPython interpreter (ideally in that it may not factually be completely compatible, but is it aimed to be completely compatible)?
No. There's a documented list of things that are different. [0] That said, you likely don't have many of these issues in your code, if any. The ideal is for folks who write portable pure Python without relying on implementation-specific details to be able to run on PyPy and CPython without any hacks.
[0] http://pypy.readthedocs.io/en/latest/cpython_differences.htm...
Thanks for the link!
basically yes, with caveats, the big gotcha is C libraries exposed to python. CFFI helps alleviate this issue, but it's not a 100% identical replacement for the c bindings that CPython gives you. See their website for all the details.