2.2.1 错误处理 Error Handling

When an error occurs, the interpreter prints an error message and a stack trace. In interactive mode, it then returns to the primary prompt; when input came from a file, it exits with a nonzero exit status after printing the stack trace. (Exceptions handled by an except clause in a try statement are not errors in this context.) Some errors are unconditionally fatal and cause an exit with a nonzero exit; this applies to internal inconsistencies and some cases of running out of memory. All error messages are written to the standard error stream; normal output from the executed commands is written to standard output.

有错误发生时，解释器打印一个错误信息和栈跟踪（监视）器？。交互模式下，它返回主提示符，如果从文件输入执行，它在打印栈跟踪器后以非零状态退出。（异常可以由 try 语句中的 except 子句来控制，这样就不会出现上文中的错误信息）有一些非常致命的错误会导致非零状态下退出，这由通常由内部矛盾和内存溢出造成。所有的错误信息都写入标准错误流；命令中执行的普通输出写入标准输出。

Typing the interrupt character (usually Control-C or DEL) to the primary or secondary prompt cancels the input and returns to the primary prompt.^2.1Typing an interrupt while a command is executing raises the KeyboardInterrupt exception, which may be handled by a try statement.

在主提示符或附属提示符输入中断符（通常是Control-C or DEL）就会取消当前输入，回到主命令行。 ^2.2.执行命令时输入一个中断符会抛出一个 KeyboardInterrupt 异常，它可以被 try 句截获。

注脚

... prompt.^2.1: A problem with the GNU Readline package may prevent this.
... DEL）就会取消当前输入，回到主命令行。^2.2: GNU readline 包的一个错误可能会造成无法正常工作。