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, bobbyi, gregory.p.smith, jcea, lesha, neologix, nirai, pitrou, sbt, sdaoden, vinay.sajip, vstinner
Date 2012-06-02.14:49:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
>  Use file locks in logging, whenever possible.

Logging doesn't just log to files, and moreover, also has locks to serialise access to internal data structures (nothing to do with files). Hence, using file locks in logging is not going to magically solve problems caused in threading+forking scenarios.

Apart from logging a commonly used part of the stdlib library which uses locks, I don't think this issue is to do with logging, specifically; logging uses locks in an unexceptional, conventional way, much as any other code might. Whatever solution is come up with for this thorny issue, it needs to be generic, in my view; otherwise we might just be papering over the cracks.
Date User Action Args
2012-06-02 14:49:29vinay.sajipsetrecipients: + vinay.sajip, gregory.p.smith, jcea, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, lesha
2012-06-02 14:49:29vinay.sajipsetmessageid: <>
2012-06-02 14:49:28vinay.sajiplinkissue6721 messages
2012-06-02 14:49:28vinay.sajipcreate