Vinay Sajip [EMAIL PROTECTED] added the comment:
This is not a logging bug, but rather due to the circumstance that
.pyc/.pyo files do not correctly point to the source files that produced
them. There is another issue about this (#1180193) .
Closing this, as it's not a logging issue.
Vinay Sajip [EMAIL PROTECTED] added the comment:
Can you confirm whether this problem occurs even after deleting all .pyc
and .pyo files, including in the Python library folders and your
application folders? Also, which specific platform is this happening on?
On your installation, is the line
Charles Merriam [EMAIL PROTECTED] added the comment:
In my installation, line 1327 is within the logging.debug() function,
specifically at the
call to apply(root.debug, (msg,)+args, kwargs)
[EMAIL PROTECTED]:~/py$ rm *.pyc
[EMAIL PROTECTED]:~/py$ python x.py
New submission from Charles Merriam [EMAIL PROTECTED]:
About same as problem in 2.4 Issue1470422 closed without a test case on
MacOS X/Python 2.4.
Also same as
http://mail.python.org/pipermail/python-bugs-list/2004-July/024111.html
and so on back for years.
What happens:
[EMAIL
Charles Merriam [EMAIL PROTECTED] added the comment:
oops, last line should be exits the stack frames for the logging
module. This should be a once-per-program-execution event
Hmm.. tracker should have a preview button.
__
Tracker [EMAIL PROTECTED]
