In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
>
>I use the Threading module whenever I need to use threads. It works
>quite nicely and I have yet to have any problems with it, except for a
>little goofiness with WMI that was explained to me long ago. You might
>check that module out.
In article <[EMAIL PROTECTED]>,
enska <[EMAIL PROTECTED]> wrote:
>
>Can someone clarify the steps needed to make access to the interpreter
>safe from multiple threads?
>
>I've been reading the docs for days and I still find them very confusing
>and misleading. For example does the PyGILState_Ensur
On Oct 21, 11:25 am, enska <[EMAIL PROTECTED]> wrote:
> Can someone clarify the steps needed to make access to the interpreter
> safe from multiple threads?
>
> I've been reading the docs for days and I still find them very confusing
> and misleading. For example does the PyGILState_Ensure() functi
Can someone clarify the steps needed to make access to the interpreter
safe from multiple threads?
I've been reading the docs for days and I still find them very confusing
and misleading. For example does the PyGILState_Ensure() function lock the
GIL or just create the thread state? Is thread supp
