Message162063
| 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 |
<1338542339.74.0.762294429546.issue6721@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
>> 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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年06月01日 09:18:59 | vinay.sajip | set | recipients:
+ vinay.sajip, gregory.p.smith, jcea, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, avian, lesha |
| 2012年06月01日 09:18:59 | vinay.sajip | set | messageid: <1338542339.74.0.762294429546.issue6721@psf.upfronthosting.co.za> |
| 2012年06月01日 09:18:59 | vinay.sajip | link | issue6721 messages |
| 2012年06月01日 09:18:58 | vinay.sajip | create |
|