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 vinay.sajip
Recipients Giovanni.Bajo, avian, bobbyi, gregory.p.smith, jcea, lesha, neologix, nirai, pitrou, sbt, sdaoden, vinay.sajip, vstinner
Date 2012-06-01.09:18:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
>> Re "threading locks cannot be used to protect things outside of a
>> single process":

> The Python standard library already violates this, in that the
> "logging" module uses such a lock to protect the file/socket/whatever,
> to which it is writing.

logging is not doing anything to protect things *outside* of a single process - the logging docs make that clear, and give specific recommendations for how to use logging in a multi-process scenario. Logging is just using locks to manage contention between multiple threads in a single process. In that sense, it is no different to any other Python code that uses locks.
Date User Action Args
2012-06-01 09:18:59vinay.sajipsetrecipients: + vinay.sajip, gregory.p.smith, jcea, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, avian, lesha
2012-06-01 09:18:59vinay.sajipsetmessageid: <>
2012-06-01 09:18:59vinay.sajiplinkissue6721 messages
2012-06-01 09:18:58vinay.sajipcreate