This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Scott Arciszewski
Recipients Scott Arciszewski
Date 2018-12-27.15:50:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545925804.0.0.366688236093.issue35595@roundup.psfhosted.org>
In-reply-to
Content
I have a wsgi script writing to a log file. The contents look like this (truncated):

  File "build/bdist.linux-x86_64/egg/trac/ticket/query.py", line 284, in _count
    % sql, args)[0][0]
  File "build/bdist.linux-x86_64/egg/trac/db/api.py", line 122, in execute
    return db.execute(query, params)
  File "build/bdist.linux-x86_64/egg/trac/db/util.py", line 128, in execute
    cursor.execute(query, params if params is not None else [])

When confronted with this logfile, I have no idea where build/bdist.linux-x86_64 lives. Rather than hoping a well-timed lsof is adequate to catch the actual script path, I'd like to be able to set a sys.flag to always log the real, fullpath of the .py script either instead of, or alongside, the file path.
History
Date User Action Args
2018-12-27 15:50:11Scott Arciszewskisetrecipients: + Scott Arciszewski
2018-12-27 15:50:04Scott Arciszewskisetmessageid: <1545925804.0.0.366688236093.issue35595@roundup.psfhosted.org>
2018-12-27 15:50:03Scott Arciszewskilinkissue35595 messages
2018-12-27 15:50:03Scott Arciszewskicreate