➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients brian.curtin, kristjan.jonsson, loewis, pitrou, sbt, tim.golden
Date 2011-03-20.20:11:43
SpamBayes Score 0.00037705986
Marked as misclassified No
Message-id <1300651900.3481.33.camel@localhost.localdomain>
In-reply-to <4D865E99.4080708@v.loewis.de>
Content 
> > At that time, the Pythread_* functions were still in use by the GIL
> > implementation, and it made a difference judging by the commit message.
> 
> Hmm. And if some application uses thread.lock heavily, won't it still
> make a difference?

An acquire/release pair is less than one microsecond here. Compared to
the evaluation overhead of Python code, it seems not very significant.
That said, if someone can guarantee than the complex approach is
correct, why not.
History
Date User Action Args
2011-03-20 20:11:43pitrousetrecipients: + pitrou, loewis, kristjan.jonsson, tim.golden, brian.curtin, sbt
2011-03-20 20:11:43pitroulinkissue11618 messages
2011-03-20 20:11:43pitroucreate