Re: lxml + mod_python: cannot unmarshal code objects in restricted execution mode

>> As this takes some time I will post
>> the result later.
> Please do.

Seems to work properly. But I'm not really sure how bad
"main_interpreter" is polluted now.

> No way. There's a reason why it is there which is the same why we use it: it's
> simple and usable. Using anything else would mean a lot of rewriting.

Thats sad. What are the chances that patches addressing this problem are
accepted?
(Must review the code first, but I would really like a clean solution here)

> You might want to try compiling lxml with "--without-threading", though, which
> disables concurrency support completely (i.e. not more GIL freeing).

Works, too. But I'm not really sure it it is a good idea to do so, as
Py_NewInterpreter seems to create a thread, see
http://www.python.org/doc/current/api/initialization.html#l2h-820. But I
think this might not be a problem if not using a threaded Apache-MPM.

Greetings, David Danier