➜

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 kristjan.jonsson
Recipients Sebastian.Noack, asvetlov, jyasskin, kristjan.jonsson, mklauber, pitrou
Date 2012-09-30.11:02:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349002959.22.0.918956447587.issue8800@psf.upfronthosting.co.za>
In-reply-to
Content 
Yes, any "blocking" on the internal lock is not semantic blocking due to the use of the Shared lock itself, but merely a technical aspect, not semantically visible to the program.  It is equivalent to the operating system pausing the thread, a techical detail opaque to the user program and somethign it cannot affect or influence.

"Blocking" in the sense of the lock is due to the semantic use of the lock itself and the resources that it protects.
History
Date User Action Args
2012-09-30 11:02:39kristjan.jonssonsetrecipients: + kristjan.jonsson, pitrou, jyasskin, asvetlov, mklauber, Sebastian.Noack
2012-09-30 11:02:39kristjan.jonssonsetmessageid: <1349002959.22.0.918956447587.issue8800@psf.upfronthosting.co.za>
2012-09-30 11:02:39kristjan.jonssonlinkissue8800 messages
2012-09-30 11:02:38kristjan.jonssoncreate