Le 08/04/2012 02:56, Vinay Sajip a écrit :
Thibaut gmail.com> writes:
This is exactly what I wanted, it seems perfect. However I still have a
question, from what I understood,
I have to configure logging AFTER creating the process, to avoid
children process to inherits the logging config.
Un
Thibaut gmail.com> writes:
> This is exactly what I wanted, it seems perfect. However I still have a
> question, from what I understood,
> I have to configure logging AFTER creating the process, to avoid
> children process to inherits the logging config.
>
> Unless there is a way to "clean" lo
Thibaut gmail.com> writes:
> This is exactly what I wanted, it seems perfect. However I still have a
> question, from what I understood,
> I have to configure logging AFTER creating the process, to avoid
> children process to inherits the logging config.
>
> Unless there is a way to "clean" lo
Le 07/04/2012 16:47, Vinay Sajip a écrit :
Thibaut gmail.com> writes:
Ok, I understand what happenned. In fact, configuring the logging before
forking works fine. Subprocess inherits the configuration, as I thought.
The problem was that I didn't passed any handler to the QueueListener
constr
Thibaut gmail.com> writes:
> Ok, I understand what happenned. In fact, configuring the logging before
> forking works fine. Subprocess inherits the configuration, as I thought.
>
> The problem was that I didn't passed any handler to the QueueListener
> constructor. The when the listener reciev
Le 07/04/2012 11:22, Thibaut DIRLIK a écrit :
Hi,
I'm currently writing a multiprocess applications with Python 3.2 and
multiprocessing module. My subprocesses will use a QueueHandler to log
messages (by sending them to the main process, which uses a
QueueListener). However, if logging is alr
