Python当我捕获异常时,如何获取类型,文件和行号?

Cla*_*diu 231 python exception-handling exception stack-trace

捕获将如此打印的异常:

Traceback (most recent call last):
  File "c:/tmp.py", line 1, in <module>
    4 / 0
ZeroDivisionError: integer division or modulo by zero
Run Code Online (Sandbox Code Playgroud)

我想将其格式化为:

ZeroDivisonError, tmp.py, 1
Run Code Online (Sandbox Code Playgroud)

Ant*_*sma 339

import sys, os

try:
    raise NotImplementedError("No error")
except Exception as e:
    exc_type, exc_obj, exc_tb = sys.exc_info()
    fname = os.path.split(exc_tb.tb_frame.f_code.co_filename)[1]
    print(exc_type, fname, exc_tb.tb_lineno)
Run Code Online (Sandbox Code Playgroud)

  • 将sys.exc_info()解压缩到局部变量时应该小心,因为如果在except处理程序中得到异常,则本地变量可以保存在循环引用中而不是GC'd.最佳做法是始终只使用sys.exc_info()中的切片.或者使用其他模块,如追溯,正如其他海报所建议的那样. (47认同)
  • @DanielPryden Python文档也使用相同的解包方法https://docs.python.org/2/library/traceback.html#traceback-examples (5认同)
  • @Basj:使用sys.exc_info()[0] .__ name__,您将获得该类型的简单名称. (4认同)
  • @RobM:是的,它是线程安全的.引入了`sys.exc_info()`来处理先前API中的线程安全问题.其输出特定于当前线程和当前堆栈帧. (3认同)
  • tb 只是 exc_tb 吗?和 os.path.split(blabla)[1] 是 os.path.basename(balbal) (2认同)
  • 我从另一个文件导入一个类,当我使用此解决方案时,错误指向当前文件中调用该类的函数的行。实际错误发生在类文件中,但此解决方案仅显示当前文件中的错误。有什么办法可以深入挖掘吗? (2认同)

nu *_*est 82

最简单的形式,对我有用.

import traceback

try:
    print(4/0)
except ZeroDivisionError:
    print(traceback.format_exc())
Run Code Online (Sandbox Code Playgroud)

产量

Traceback (most recent call last):
  File "/path/to/file.py", line 51, in <module>
    print(4/0)
ZeroDivisionError: division by zero

Process finished with exit code 0
Run Code Online (Sandbox Code Playgroud)

  • 您还可以使用“traceback.print_exc()”,而不使用“print()”。节省一些打字时间:) (10认同)
  • 虽然不完全是操作所需的格式,但这是最简单,最强大的解决方案 (3认同)
  • @jouell 嘿,我有时也喜欢用花哨的词:) (3认同)
  • 有什么强大的呢? (2认同)
  • 它只是更坚固。高速率答案无法打印我的程序中最深的堆栈。 (2认同)

pyt*_*rry 45

用于traceback.format_exception()和被调用/相关函数的(Py v2.7.3)有很大帮助.令人尴尬的是,我总是忘记阅读源头.在我徒劳地搜索类似的细节之后,我才这样做了.一个简单的问题,"如何为异常重新创建与Python相同的输出,具有所有相同的细节?" 无论他们想要什么,这都可以让任何人获得90 +%.沮丧,我想出了这个例子.我希望它能帮助别人.(它确实帮助了我!;-)

import sys, traceback

traceback_template = '''Traceback (most recent call last):
  File "%(filename)s", line %(lineno)s, in %(name)s
%(type)s: %(message)s\n''' # Skipping the "actual line" item

# Also note: we don't walk all the way through the frame stack in this example
# see hg.python.org/cpython/file/8dffb76faacc/Lib/traceback.py#l280
# (Imagine if the 1/0, below, were replaced by a call to test() which did 1/0.)

try:
    1/0
except:
    # http://docs.python.org/2/library/sys.html#sys.exc_info
    exc_type, exc_value, exc_traceback = sys.exc_info() # most recent (if any) by default

    '''
    Reason this _can_ be bad: If an (unhandled) exception happens AFTER this,
    or if we do not delete the labels on (not much) older versions of Py, the
    reference we created can linger.

    traceback.format_exc/print_exc do this very thing, BUT note this creates a
    temp scope within the function.
    '''

    traceback_details = {
                         'filename': exc_traceback.tb_frame.f_code.co_filename,
                         'lineno'  : exc_traceback.tb_lineno,
                         'name'    : exc_traceback.tb_frame.f_code.co_name,
                         'type'    : exc_type.__name__,
                         'message' : exc_value.message, # or see traceback._some_str()
                        }

    del(exc_type, exc_value, exc_traceback) # So we don't leave our local labels/objects dangling
    # This still isn't "completely safe", though!
    # "Best (recommended) practice: replace all exc_type, exc_value, exc_traceback
    # with sys.exc_info()[0], sys.exc_info()[1], sys.exc_info()[2]

    print
    print traceback.format_exc()
    print
    print traceback_template % traceback_details
    print
Run Code Online (Sandbox Code Playgroud)

在具体回答此查询:

sys.exc_info()[0].__name__, os.path.basename(sys.exc_info()[2].tb_frame.f_code.co_filename), sys.exc_info()[2].tb_lineno
Run Code Online (Sandbox Code Playgroud)

  • 将 py3 的 `'message' : exc_value.message` 更改为 `'message' : str(exc_value)` (3认同)

Str*_*ker 31

以下是显示异常发生位置的行号的示例.

import sys
try:
    print(5/0)
except Exception as e:
    print('Error on line {}'.format(sys.exc_info()[-1].tb_lineno), type(e).__name__, e)

print('And the rest of program continues')
Run Code Online (Sandbox Code Playgroud)


Chr*_*ian 14

您无需导入回溯即可实现此目的:

try:
    func1()
except Exception as ex:
    trace = []
    tb = ex.__traceback__
    while tb is not None:
        trace.append({
            "filename": tb.tb_frame.f_code.co_filename,
            "name": tb.tb_frame.f_code.co_name,
            "lineno": tb.tb_lineno
        })
        tb = tb.tb_next
    print(str({
        'type': type(ex).__name__,
        'message': str(ex),
        'trace': trace
    }))
Run Code Online (Sandbox Code Playgroud)

输出:

{

  'type': 'ZeroDivisionError',
  'message': 'division by zero',
  'trace': [
    {
      'filename': '/var/playground/main.py',
      'name': '<module>',
      'lineno': 16
    },
    {
      'filename': '/var/playground/main.py',
      'name': 'func1',
      'lineno': 11
    },
    {
      'filename': '/var/playground/main.py',
      'name': 'func2',
      'lineno': 7
    },
    {
      'filename': '/var/playground/my.py',
      'name': 'test',
      'lineno': 2
    }
  ]
}
Run Code Online (Sandbox Code Playgroud)


Luc*_*Luc 10

没有任何导入,但也与导入的模块不兼容:

try:
    raise TypeError("Hello, World!")  # line 2
except Exception as e:
    print(
        type(e).__name__,          # TypeError
        __file__,                  # /tmp/example.py
        e.__traceback__.tb_lineno  # 2
    )
Run Code Online (Sandbox Code Playgroud)

$ python3 /tmp/example.py
TypeError /tmp/example.py 2

重申一下,这确实不是整个工作importS或模块,因此,如果你这样做import X; try: X.example();,则文件名和行号将指向包含该行X.example(),而不是哪里出了问题行 X.example()。如果有人知道如何从最后一个堆栈跟踪行轻松获取文件名和行号(我期待类似e[-1].filename,但没有这样的运气),请改进此答案。

  • 我认为 `e.__traceback__.tb_frame.f_code.co_filename` 可能可以解决文件名的问题。 (4认同)