On Jul 31, 2:04 pm, Jean-Michel Pichavant
wrote:
> Jannik Sundø wrote:
> > Hi all. I think I fixed this problem by setting fileLogger.propagate =
> > 0. Otherwise it will propagate up to the root logger, which outputs to
> > stdout, as far as I can understand.
>
> > On 31 Jul 2009, at 01:17, Janni
Jannik Sundø wrote:
Hi all. I think I fixed this problem by setting fileLogger.propagate =
0. Otherwise it will propagate up to the root logger, which outputs to
stdout, as far as I can understand.
On 31 Jul 2009, at 01:17, Jannik Sundø wrote:
Dear all, I am quite confused about the Python l
On Jul 31, 12:41 pm, Jannik Sundø wrote:
> Hi all. I think I fixed this problem by setting fileLogger.propagate =
> 0. Otherwise it will propagate up to the root logger, which outputs to
> stdout, as far as I can understand.
>
Only if you specifically configure it to do so - for example, call
Hi all. I think I fixed this problem by setting fileLogger.propagate =
0. Otherwise it will propagate up to the root logger, which outputs to
stdout, as far as I can understand.
On 31 Jul 2009, at 01:17, Jannik Sundø wrote:
Dear all, I am quite confused about the Python logging. I have read
Jannik Sundø wrote:
> Dear all, I am quite confused about the Python logging. I have read
> and re-read the Python documentation for the Python logging module and
> googled, but to no avail. I simply want one logger to log to a file
> and another logger to log to the console. Neither should log th
Dear all, I am quite confused about the Python logging. I have read
and re-read the Python documentation for the Python logging module and
googled, but to no avail. I simply want one logger to log to a file
and another logger to log to the console. Neither should log the
other's messages. T