"michael gross" wrote:

>  unfortunately it turned out that the c extentions of pil do not support
>  multithreading.

most heavy PIL operations release the global interpreter lock (GIL), if
that's what you mean.

that doesn't mean that Python code using PIL will be fully multithreaded,
though - the interpreter still uses the interpreter lock to serialize access
to the virtual machine.  there's not much I can do about that in PIL.

can you provide more details on what kind of operations you're using,
and what makes you think that it's PIL itself that causes the problems.

</F> 



_______________________________________________
Image-SIG maillist  -  Image-SIG@[...].org
http://mail.python.org/mailman/listinfo/image-sig