[issue16368] error when logging message

2012-10-30 Thread R. David Murray
R. David Murray added the comment: Yep, that would do it. format is supposed to be a format string. -- status: open -> closed ___ Python tracker ___

[issue16368] error when logging message

2012-10-30 Thread Tom Kuiper
Tom Kuiper added the comment: On 10/30/2012 05:29 PM, R. David Murray wrote: > R. David Murray added the comment: > > Do none of those submodules import logging? > > It is unlikely that this is a Python bug. Somewhere _fmt is getting set to > an integer. The way to prove this one way or anothe

[issue16368] error when logging message

2012-10-30 Thread Tom Kuiper
Tom Kuiper added the comment: Give me a few moments to dig further. I may have found the submodule culprit. Checking. Tom On 10/30/2012 05:29 PM, R. David Murray wrote: > R. David Murray added the comment: > > Do none of those submodules import logging? > > It is unlikely that this is a Pyth

[issue16368] error when logging message

2012-10-30 Thread R. David Murray
R. David Murray added the comment: Do none of those submodules import logging? It is unlikely that this is a Python bug. Somewhere _fmt is getting set to an integer. The way to prove this one way or another is to start deleting things until you find the code that is triggering the issue. --

[issue16368] error when logging message

2012-10-30 Thread Tom Kuiper
New submission from Tom Kuiper: This error comes from the logging module when a message is logged, but only when I also import another module which does use logging at all: Traceback (most recent call last): File "/usr/lib/python2.6/logging/__init__.py", line 776, in emit msg = self.forma