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 jango
Recipients jango, pitrou
Date 2011-12-09.23:20:19
SpamBayes Score 2.14616e-11
Marked as misclassified No
Message-id <>
In-reply-to <>
Hi Antoine,

* If I don't pass a logger and do print statements instead, works like a 

* If I getLogger() in the child instead, example fails with the same trace.

However, according to this ( 
): "The logging module is intended to be thread-safe without any special 
work needing to be done by its clients. It achieves this though using 
threading locks; there is one lock to serialize access to the module’s 
shared data, and each handler also creates a lock to serialize access to 
its underlying I/O."

Which is why I assumed I could use logging safely.


On 11-12-09 04:30 PM, Antoine Pitrou wrote:
> Antoine Pitrou<>  added the comment:
> I don't think it's the queue. Try removing the logger instead (or creating it in the child).
> ----------
> _______________________________________
> Python tracker<>
> <>
> _______________________________________
Date User Action Args
2011-12-09 23:20:20jangosetrecipients: + jango, pitrou
2011-12-09 23:20:19jangolinkissue13569 messages
2011-12-09 23:20:19jangocreate