[Python-ideas] In-process interpreters

Terry Reedy tjreedy at udel.edu
Fri Nov 19 04:02:55 CET 2010

On 11/18/2010 4:08 AM, Tim Lesher wrote:
> 2010/11/18 Kristján Valur Jónsson<kristjan-hPzAiOG7rkJWk0Htik3J/w at public.gmane.org>:
>> This is one of the things I’d have liked to see as part of py3k:  “fixing”
>> python for embedding in applications and defices.
> My current work project has similar issues (also an embedded Python on
> embedded hardware). We've examined Py_Initialize()/Py_Finalize()
> pairing, subinterpreters, and out-of-proc interpreters, and are in the
> same predicament.
> I believe one of the main difficulties will be doing it in a way that
> doesn't penalize the 99% use case that most of the Python world
> experiences (one interpreter/one process, named python).  That's been,
> for example, the fatal issue with most of the efforts to eliminate the
> global interpreter lock.
> It doesn't matter how nice it makes life for us if it causes
> performance or other headaches for the vast majority of Python users.

I keep wondering whether it would be possible to rearrange the current 
code in any way that a) would not hinder performance significantly but 
b) would make it easier to maintain patches for compiler variations for 
the minority use cases.

Terry Jan Reedy

More information about the Python-ideas mailing list