In my opinion errors have a reason to appear, that my sound stupid, but thats the way it is. Good programming only raises errors when you have to handle them. Also, as i read some time ago, "the pass-Statement is a Statement that Shows code will be inserted later", so if you want to have an empty except-statement feel free to do so, but for a good program there will be a part missing. because you dont handle the things you should have. Appearing exceptions give you the chance to correct input data or to change your data structure so these exceptions dont occur again (but in most cases (Network-exceptions, General input-exceptions) exceptions indicate that the next parts of the program wont execute well. For example a NetworkException can indicate a broken network-connection and the program cant send/recieve data in the next program steps.

但是只对一个执行块使用pass块是有效的，因为你仍然可以区分不同类型的异常，所以如果你把所有的异常块放在一个中，它就不是空的:

try:
    #code here
except Error1:
    #exception handle1

except Error2:
    #exception handle2
#and so on

可以写成这样:

try:
    #code here
except BaseException as e:
    if isinstance(e, Error1):
        #exception handle1

    elif isinstance(e, Error2):
        #exception handle2

    ...

    else:
        raise

因此，即使是多个带有pass语句的异常块也可能导致代码，其结构处理特殊类型的异常。

except:pass构造本质上是在运行try:块中包含的代码时，使出现的任何和所有异常条件保持沉默。

这种糟糕的做法是因为它通常不是你真正想要的。更常见的情况是，出现一些特定的情况，你想要保持沉默，除了:pass是一个太生硬的工具。它将完成工作，但它也会掩盖其他错误条件，您可能没有预料到，但可能非常希望以其他方式处理。

What makes this particularly important in Python is that by the idioms of this language, exceptions are not necessarily errors. They're often used this way, of course, just as in most languages. But Python in particular has occasionally used them to implement an alternative exit path from some code tasks which isn't really part of the normal running case, but is still known to come up from time to time and may even be expected in most cases. SystemExit has already been mentioned as an old example, but the most common example nowadays may be StopIteration. Using exceptions this way caused a lot of controversy, especially when iterators and generators were first introduced to Python, but eventually the idea prevailed.

首先，它违背了Python的两个禅宗原则:

显性比隐性好 错误绝不能悄无声息地过去

它的意思是，你故意让你的错误悄无声息地过去。此外，您不知道究竟发生了哪个错误，因为except: pass将捕获任何异常。

其次，如果我们试图从Python的禅意中抽象出来，而只是从理智的角度来说话，你应该知道，使用except:pass会让你在系统中失去知识和控制。经验法则是，如果发生错误，就引发异常，并采取适当的操作。如果你事先不知道这些操作应该是什么，至少在某个地方记录错误(最好重新引发异常):

try:
    something
except:
    logger.exception('Something happened')

但是，通常情况下，如果您试图捕获任何异常，那么您可能正在做错误的事情!

我个人更喜欢这个解决方案:

except ValueError as error:
                print(error.args)
                pass

错误。Args给了我一个简单的代码行，它不会太分散人的注意力，但确实有助于代码审查，特别是如果错误有不同的原因，比如

(ValueError('year 0 is out of range'),)
(ValueError('month must be in 1..12'),)
(ValueError('day is out of range for month'),)

当研究熊猫的时间周期时。

你至少应该使用except Exception:来避免捕获系统异常，如SystemExit或KeyboardInterrupt。这里是文档链接。

一般来说，您应该显式地定义想要捕获的异常，以避免捕获不想要的异常。您应该知道您忽略了哪些异常。

通常，您可以将任何错误/异常分为以下三类之一:

Fatal: Not your fault, you cannot prevent them, you cannot recover from them. You should certainly not ignore them and continue, and leave your program in an unknown state. Just let the error terminate your program, there is nothing you can do. Boneheaded: Your own fault, most likely due to an oversight, bug or programming error. You should fix the bug. Again, you should most certainly not ignore and continue. Exogenous: You can expect these errors in exceptional situations, such as file not found or connection terminated. You should explicitly handle these errors, and only these.

在除了:pass之外的所有情况下，pass只会让你的程序处于未知状态，在这种状态下它会造成更多的损害。