最好和最准确的理解pass的方式是显式地告诉解释器什么都不做。以同样的方式输入以下代码:

def foo(x,y):
    return x+y

意思是“如果我调用函数foo(x, y)，将标签x和y所代表的两个数字相加并返回结果”，

def bar():
    pass

意思是“如果我调用函数栏()，什么都不做。”

其他答案都很正确，但它也适用于一些不涉及占位的事情。

例如，在我最近编写的一段代码中，有必要对两个变量进行除法，并且除数可能为零。

c = a / b

显然，如果b为零，将产生一个ZeroDivisionError。在这种特殊情况下，在b为零的情况下，让c为零是理想的行为，所以我使用了以下代码:

try:
    c = a / b
except ZeroDivisionError:
    pass

另一种不太标准的用法是为调试器放置断点。例如，我想要一段代码在For语句的第20次迭代时进入调试器。在声明。所以:

for t in range(25):
    do_a_thing(t)
    if t == 20:
        pass

在传递时使用断点。

在Python中，pass基本上什么都不做，但与注释不同的是，它不会被解释器忽略。所以你可以在很多地方利用它，把它变成占位符:

1:可以在课堂上使用

class TestClass:
    pass

2:可以在循环语句和条件语句中使用:

if (something == true):  # used in conditional statement
    pass

while (some condition is true):  # user is not sure about the body of the loop
    pass

3:可用于功能:

def testFunction(args): # The programmer wants to implement the body of the function later
    pass

当程序员暂时不想给出实现，但仍然想创建某个类/函数/条件语句以供以后使用时，通常使用Pass。由于Python解释器不允许出现空白或未实现的类、函数或条件语句，因此会给出一个错误:

IndentationError:期望一个缩进的块

Pass可以在这种情况下使用。

最好和最准确的理解pass的方式是显式地告诉解释器什么都不做。以同样的方式输入以下代码:

def foo(x,y):
    return x+y

意思是“如果我调用函数foo(x, y)，将标签x和y所代表的两个数字相加并返回结果”，

def bar():
    pass

意思是“如果我调用函数栏()，什么都不做。”

其他答案都很正确，但它也适用于一些不涉及占位的事情。

例如，在我最近编写的一段代码中，有必要对两个变量进行除法，并且除数可能为零。

c = a / b

显然，如果b为零，将产生一个ZeroDivisionError。在这种特殊情况下，在b为零的情况下，让c为零是理想的行为，所以我使用了以下代码:

try:
    c = a / b
except ZeroDivisionError:
    pass

另一种不太标准的用法是为调试器放置断点。例如，我想要一段代码在For语句的第20次迭代时进入调试器。在声明。所以:

for t in range(25):
    do_a_thing(t)
    if t == 20:
        pass

在传递时使用断点。

pass用于避免Python中的缩进错误。

如果我们以C、c++和Java等语言为例，它们有这样的大括号:

 if(i==0)
 {}
 else
 {//some code}

但是在Python中，我们使用缩进代替大括号，所以为了避免这样的错误，我们使用pass。

记得你在做测验的时候

if(dont_know_the_answer)
    pass

示例程序,

for letter in 'geeksforgeeks':
    pass
print 'Last letter: ', letter

Python在语法上要求代码块(在if, except, def, class等之后)不能为空。然而，空代码块在各种不同的上下文中都很有用，比如下面的例子，这是我见过的最常见的用例。

因此，如果在代码块中不希望发生任何事情，则需要一个传递以使该代码块不产生IndentationError。或者，任何语句(包括一个要求值的项，如Ellipsis字面量…)可以使用字符串(通常是docstring)，但该传递清楚地表明，实际上不应该发生任何事情，也不需要实际计算并(至少暂时)存储在内存中。

Ignoring (all or) a certain type of Exception (example from xml): try: self.version = "Expat %d.%d.%d" % expat.version_info except AttributeError: pass # unknown Note: Ignoring all types of raises, as in the following example from pandas, is generally considered bad practice, because it also catches exceptions that should probably be passed on to the caller, e.g. KeyboardInterrupt or SystemExit (or even HardwareIsOnFireError – How do you know you aren't running on a custom box with specific errors defined, which some calling application would want to know about?). try: os.unlink(filename_larry) except: pass Instead using at least except Error: or in this case preferably except OSError: is considered much better practice. A quick analysis of all Python modules I have installed gave me that more than 10% of all except ...: pass statements catch all exceptions, so it's still a frequent pattern in Python programming. Deriving an exception class that does not add new behaviour (e.g., in SciPy): class CompileError(Exception): pass Similarly, classes intended as abstract base class often have an explicit empty __init__ or other methods that subclasses are supposed to derive (e.g., pebl): class _BaseSubmittingController(_BaseController): def submit(self, tasks): pass def retrieve(self, deferred_results): pass Testing that code runs properly for a few test values, without caring about the results (from mpmath): for x, error in MDNewton(mp, f, (1,-2), verbose=0, norm=lambda x: norm(x, inf)): pass In class or function definitions, often a docstring is already in place as the obligatory statement to be executed as the only thing in the block. In such cases, the block may contain pass in addition to the docstring in order to say “This is indeed intended to do nothing.”, for example in pebl: class ParsingError(Exception): """Error encountered while parsing an ill-formed datafile.""" pass In some cases, pass is used as a placeholder to say “This method/class/if-block/... has not been implemented yet, but this will be the place to do it”, although I personally prefer the Ellipsis literal ... in order to strictly differentiate between this and the intentional “no-op” in the previous example. (Note that the Ellipsis literal is a valid expression only in Python 3) For example, if I write a model in broad strokes, I might write def update_agent(agent): ... where others might have def update_agent(agent): pass before def time_step(agents): for agent in agents: update_agent(agent) as a reminder to fill in the update_agent function at a later point, but run some tests already to see if the rest of the code behaves as intended. (A third option for this case is raise NotImplementedError. This is useful in particular for two cases: Either “This abstract method should be implemented by every subclass, and there isn't a generic way to define it in this base class”, or “This function, with this name, is not yet implemented in this release, but this is what its signature will look like”)

Pass只是空的表示代码。

例如，pass用于创建一个空类或函数，如下所示:

class Test:
    pass

def test():
    pass

但是，如果一个类或函数真的没有任何东西，甚至通过如下所示:

class Test:
    # pass

def test():
    # psss

出现如下错误:

SyntaxError:解析时意外的EOF

正如我之前所说，pass只是空的指示代码，所以如果在pass之后有一些代码，代码的工作方式如下所示:

class Test:
    pass
    x = "Hello World"

def test():
    pass
    return "Hello World"

print(Test.x) # Hello World
print(test()) # Hello World