Speeding up CPython

Posted Dec 17, 2020 11:57 UTC (Thu) by renejsum (guest, #124634)
In reply to: Speeding up CPython by mathstuf
Parent article: Speeding up CPython

I don't understand why PyPy is not pushed as the default VM for Python. It's written in RPython, it's fast, it's compatible....

Speeding up CPython

Posted Dec 17, 2020 12:52 UTC (Thu) by mathstuf (subscriber, #69389) [Link] (2 responses)

How do I embed a PyPy interpreter into an executable? Without an API to do so, CPython is the only answer there (or IronPython/Jython if your app is in those language families).

I do see https://doc.pypy.org/en/latest/embedding.html but it being marked as deprecated without a link to a replacement isn't promising…

Even then, distribution of an embedded Python environment is a nightmare with CPython, but it's a (mostly) known one at this point. Unless PyPy makes that vastly easier, I don't want to have to slay another dragon :/ .

Speeding up CPython

Posted Dec 24, 2020 10:13 UTC (Thu) by njs (subscriber, #40338) [Link] (1 responses)

The link could be more prominent, but that page does link to the new and supported pypy embedding interface:

https://cffi.readthedocs.io/en/latest/embedding.html

Speeding up CPython

Posted Dec 26, 2020 0:14 UTC (Sat) by mathstuf (subscriber, #69389) [Link]

This is fine, but not suitable (at all) for what I'm talking about. It looks like for any Python library we'd want to provide, we'd have to write some cffi code. No one is going to do that for matplotlib, numpy, scipy, or the umpteen other libraries we get asked to provide in our package.