大多数答案指向except(…)as(…):语法(正确)，但同时没有人想谈论房间里的大象，而大象是sys.exc_info()函数。 来自sys模块的文档(重点是我的):

This function returns a tuple of three values that give information about the exception that is currently being handled. (…) If no exception is being handled anywhere on the stack, a tuple containing three None values is returned. Otherwise, the values returned are (type, value, traceback). Their meaning is: type gets the type of the exception being handled (a subclass of BaseException); value gets the exception instance (an instance of the exception type); traceback gets a traceback object (see the Reference Manual) which encapsulates the call stack at the point where the exception originally occurred.

我认为sys.exc_info()可以被视为对原始问题“我如何知道发生了什么类型的异常?”的最直接答案。

希望这对你有帮助

import sys
varExcepHandling, varExcepHandlingZer = 2, 0
try:
  print(varExcepHandling/varExcepHandlingZer)
except Exception as ex: 
  print(sys.exc_info())

'sys.exc_info()'将返回一个元组，如果你只想要异常类名，请使用'sys.exc_info()[0]'

注意:-如果你想看到所有的异常类，只需写入dir(__builtin__)

其他答案都指出不应该捕获通用异常，但似乎没有人愿意告诉您原因，这对于理解何时可以打破“规则”至关重要。下面是一个解释。基本上，这样你就不会隐藏:

发生错误的事实 发生错误的细节(错误隐藏反模式)

因此，只要您注意不做这些事情，就可以捕获泛型异常。例如，你可以用另一种方式向用户提供异常信息，比如:

在GUI中以对话框的形式显示异常 将异常从工作线程或进程转移到多线程或多处理应用程序中的控制线程或进程

那么如何捕捉泛型异常呢?有几种方法。如果你只想要一个异常对象，可以这样做:

try:
    someFunction()
except Exception as ex:
    template = "An exception of type {0} occurred. Arguments:\n{1!r}"
    message = template.format(type(ex).__name__, ex.args)
    print message

Make sure message is brought to the attention of the user in a hard-to-miss way! Printing it, as shown above, may not be enough if the message is buried in lots of other messages. Failing to get the users attention is tantamount to swallowing all exceptions, and if there's one impression you should have come away with after reading the answers on this page, it's that this is not a good thing. Ending the except block with a raise statement will remedy the problem by transparently reraising the exception that was caught.

上述用法和使用just except: without any argument的区别有两个方面:

裸except:不提供要检查的异常对象 异常SystemExit, KeyboardInterrupt和GeneratorExit不会被上面的代码捕获，这通常是你想要的。参见异常层次结构。

如果你也想要与你没有捕获异常时得到的stacktrace相同，你可以像这样得到(仍然在except子句中):

import traceback
print traceback.format_exc()

如果你使用logging模块，你可以像这样将异常输出到日志中(以及一条消息):

import logging
log = logging.getLogger()
log.exception("Message for you, sir!")

如果你想更深入地研究堆栈，查看变量等，可以使用except块内pdb模块的post_mortem函数:

import pdb
pdb.post_mortem()

我发现最后一种方法在查找bug时非常有用。

这些答案很适合调试，但对于以编程方式测试异常，isinstance(e, SomeException)可能很方便，因为它也测试SomeException的子类，因此您可以创建应用于异常层次结构的功能。

为了补充Lauritz的答案，我创建了一个用于异常处理的装饰器/包装器，并且包装器记录发生了哪种类型的异常。

class general_function_handler(object):
    def __init__(self, func):
        self.func = func
    def __get__(self, obj, type=None):
        return self.__class__(self.func.__get__(obj, type))
    def __call__(self, *args, **kwargs):
        try:
            retval = self.func(*args, **kwargs)
        except Exception, e :
            logging.warning('Exception in %s' % self.func)
            template = "An exception of type {0} occured. Arguments:\n{1!r}"
            message = template.format(type(e).__name__, e.args)
            logging.exception(message)
            sys.exit(1) # exit on all exceptions for now
        return retval

这可以在类方法或带有装饰器的独立函数上调用:

@general_function_handler

完整的例子请参阅我的博客:http://ryaneirwin.wordpress.com/2014/05/31/python-decorators-and-exception-handling/

你可以像Lauritz推荐的那样开始:

except Exception as ex:

然后像这样打印ex:

try:
    #your try code here
except Exception as ex:
    print ex