global interpreter lock not working as it should

Martin v. Löwis loewis at informatik.hu-berlin.de
Wed Jul 31 05:36:02 EDT 2002


Paul Rubin <phr-n2002b at NOSPAMnightsong.com> writes:

> But that is precisely the gripe about the GIL.  If you have multiple
> CPU's, you can use them with C threads but not with Python threads.

That is the general gripe about the GIL, yes - but not the one of the
OP. The OP wants a pthread_yield call to be inserted in some place; he
appears not to be worried about the fact that there is a global lock
in the first place.

Regards,
Martin




More information about the Python-list mailing list