News for hackers. Stuff that matters.
Re:Embedding PyPy in a C application by kensai on Sunday May 15, 2016 @11:05AM (#11701166)
"With only a few lines of code we have written a C program that fires up a PyPy interpreter and runs our Python code as if it was a native C function. Of course I've only shown you the basics here, but the technology is really powerful."

So, C speed with Python semantics?

Re:Embedding PyPy in a C application by scandinavian on Sunday May 15, 2016 @02:16PM (#11702015)
"So, C speed with Python semantics?"

That's already what PyPy is, isn't it? (Not really C speed, but the method in the article is just calling the PyPy interpreter, so it's not quite C speed anyway.)

Re:Embedding PyPy in a C application by guipsp on Sunday May 15, 2016 @11:42AM (#11701308)
Scripting apis are a possible use too.
Re:Embedding PyPy in a C application by thedjinn on Sunday May 15, 2016 @11:45AM (#11701326)
Yes indeed, and using this approach you can also write Python plugins for other applications if they don't have Python scripting support already.
Re:Embedding PyPy in a C application by noahdesu on Sunday May 15, 2016 @03:15PM (#11702284)
In the article, after the pypy plugin.py step that produced the C library, one could presumably dlopen the library to accomplish a dynamic plugin feature. Is there a way to invoke pypy to JIT this code to avoid invoking pypy and a compiler?
Re:Embedding PyPy in a C application by thedjinn on Sunday May 15, 2016 @03:24PM (#11702320)
The way I understand it is that on first invocation of a function exported in the library this function will spin up a regular PyPy interpreter, which does JIT in exactly the same way as a normal invocation of PyPy would.