sj wrote:
> Thanks, but my point wasn't fixing the bug. I'd like the logging
> module to raise an exception on this occasion (rather than print and
> consume the error) so that I can find the bug easily. If those two
> lines were part of 10,000-line code, I'd have to check all logging
> statemen
Thanks, but my point wasn't fixing the bug. I'd like the logging
module to raise an exception on this occasion (rather than print and
consume the error) so that I can find the bug easily. If those two
lines were part of 10,000-line code, I'd have to check all logging
statements one-by-one.
--
h
make the second statement 'logging.info("%d %d", 1, 2)' or
'logging.info("%d %d %d", 1, 2, 3)', and all works. for every argument
you want to log you need one format specifier
--
http://mail.python.org/mailman/listinfo/python-list
