News for hackers. Stuff that matters.
Re:Inside cpyext: Why emulating CPython C API is so Hard by robmccoll on Friday September 21, 2018 @03:53PM (#18042188)
It seems like it would be easier and more performant (begin heresy and likely vast oversimplification) for PyPy to have a mostly complete implementation of CPython that it interacts with at the object level such that each object in PyPy could be a PyPy GC object descended from W_root or a CPython RefCount object implemented on PyObject*. There would be many points where you would still have to convert to make operations work. Either way, running under the assumption of "objects from CPython or objects that are passed to CPython are more likely to interact with other CPython objects, so lets not convert them back until we have to" might result in closer to CPython performance for code with a lot of CPython extensions.

Does this seem reasonable? Is this even possible? I don't know much about the internals of PyPy...

Re:Inside cpyext: Why emulating CPython C API is so Hard by antt on Friday September 21, 2018 @10:10PM (#18044083)
PyPy in general has much better performance than CPython.