Nikita Pchelin <nikita.pche...@gmail.com> added the comment: Hi Antoine,
* If I don't pass a logger and do print statements instead, works like a charm. * If I getLogger() in the child instead, example fails with the same trace. However, according to this ( http://docs.python.org/library/logging.html ): "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. Thanks, Nikita On 11-12-09 04:30 PM, Antoine Pitrou wrote: > Antoine Pitrou<pit...@free.fr> added the comment: > > I don't think it's the queue. Try removing the logger instead (or creating it > in the child). > > ---------- > > _______________________________________ > Python tracker<rep...@bugs.python.org> > <http://bugs.python.org/issue13569> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13569> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
