SWAMPy

✎ CARVE FLESH

EDITING: errors.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="X-UA-Compatible" content="IE=Edge" />
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 <title>8. Errors and Exceptions &#8212; Python 3.6.7 documentation</title>
 <link rel="stylesheet" href="../_static/pydoctheme.css" type="text/css" />
 <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
 <script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
 <script type="text/javascript" src="../_static/jquery.js"></script>
 <script type="text/javascript" src="../_static/underscore.js"></script>
 <script type="text/javascript" src="../_static/doctools.js"></script>
 <script type="text/javascript" src="../_static/sidebar.js"></script>
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 3.6.7 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="index" title="Index" href="../genindex.html" />
 <link rel="search" title="Search" href="../search.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="next" title="9. Classes" href="classes.html" />
 <link rel="prev" title="7. Input and Output" href="inputoutput.html" />
 <link rel="shortcut icon" type="image/png" href="../_static/py.png" />
 <link rel="canonical" href="https://docs.python.org/3/tutorial/errors.html" />
 
 <script type="text/javascript" src="../_static/copybutton.js"></script>

</head><body> 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="classes.html" title="9. Classes"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="inputoutput.html" title="7. Input and Output"
 accesskey="P">previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li>
 <a href="../index.html">3.6.7 Documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" accesskey="U">The Python Tutorial</a> &#187;</li>
 <li class="right">

<div class="inline-search" style="display: none" role="search">
 <form class="inline-search" action="../search.html" method="get">
 <input placeholder="Quick search" type="text" name="q" />
 <input type="submit" value="Go" />
 <input type="hidden" name="check_keywords" value="yes" />
 <input type="hidden" name="area" value="default" />
 </form>
 </div>
 <script type="text/javascript">$('.inline-search').show(0);</script>
 |
 </li>

</ul>
 </div>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <div class="section" id="errors-and-exceptions">
<h1>8. Errors and Exceptions<a class="headerlink" href="#errors-and-exceptions" title="Permalink to this headline">¶</a></h1>
Until now error messages haven’t been more than mentioned, but if you have tried
out the examples you have probably seen some. There are (at least) two
distinguishable kinds of errors: syntax errors and exceptions.
<div class="section" id="syntax-errors">
<h2>8.1. Syntax Errors<a class="headerlink" href="#syntax-errors" title="Permalink to this headline">¶</a></h2>
Syntax errors, also known as parsing errors, are perhaps the most common kind of
complaint you get while you are still learning Python:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; while True print(&#39;Hello world&#39;)
 File &quot;&lt;stdin&gt;&quot;, line 1
 while True print(&#39;Hello world&#39;)
 ^
SyntaxError: invalid syntax
</pre></div>
</div>
The parser repeats the offending line and displays a little ‘arrow’ pointing at
the earliest point in the line where the error was detected. The error is
caused by (or at least detected at) the token preceding the arrow: in the
example, the error is detected at the function <a class="reference internal" href="../library/functions.html#print" title="print"><code class="xref py py-func docutils literal notranslate">print()</code></a>, since a colon
(<code class="docutils literal notranslate">':'</code>) is missing before it. File name and line number are printed so you
know where to look in case the input came from a script.
</div>
<div class="section" id="exceptions">
<h2>8.2. Exceptions<a class="headerlink" href="#exceptions" title="Permalink to this headline">¶</a></h2>
Even if a statement or expression is syntactically correct, it may cause an
error when an attempt is made to execute it. Errors detected during execution
are called exceptions and are not unconditionally fatal: you will soon learn
how to handle them in Python programs. Most exceptions are not handled by
programs, however, and result in error messages as shown here:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; 10 * (1/0)
Traceback (most recent call last):
 File &quot;&lt;stdin&gt;&quot;, line 1, in &lt;module&gt;
ZeroDivisionError: division by zero
&gt;&gt;&gt; 4 + spam*3
Traceback (most recent call last):
 File &quot;&lt;stdin&gt;&quot;, line 1, in &lt;module&gt;
NameError: name &#39;spam&#39; is not defined
&gt;&gt;&gt; &#39;2&#39; + 2
Traceback (most recent call last):
 File &quot;&lt;stdin&gt;&quot;, line 1, in &lt;module&gt;
TypeError: Can&#39;t convert &#39;int&#39; object to str implicitly
</pre></div>
</div>
The last line of the error message indicates what happened. Exceptions come in
different types, and the type is printed as part of the message: the types in
the example are <a class="reference internal" href="../library/exceptions.html#ZeroDivisionError" title="ZeroDivisionError"><code class="xref py py-exc docutils literal notranslate">ZeroDivisionError</code></a>, <a class="reference internal" href="../library/exceptions.html#NameError" title="NameError"><code class="xref py py-exc docutils literal notranslate">NameError</code></a> and <a class="reference internal" href="../library/exceptions.html#TypeError" title="TypeError"><code class="xref py py-exc docutils literal notranslate">TypeError</code></a>.
The string printed as the exception type is the name of the built-in exception
that occurred. This is true for all built-in exceptions, but need not be true
for user-defined exceptions (although it is a useful convention). Standard
exception names are built-in identifiers (not reserved keywords).
The rest of the line provides detail based on the type of exception and what
caused it.
The preceding part of the error message shows the context where the exception
happened, in the form of a stack traceback. In general it contains a stack
traceback listing source lines; however, it will not display lines read from
standard input.
<a class="reference internal" href="../library/exceptions.html#bltin-exceptions">Built-in Exceptions</a> lists the built-in exceptions and their meanings.
</div>
<div class="section" id="handling-exceptions">
<h2>8.3. Handling Exceptions<a class="headerlink" href="#handling-exceptions" title="Permalink to this headline">¶</a></h2>
It is possible to write programs that handle selected exceptions. Look at the
following example, which asks the user for input until a valid integer has been
entered, but allows the user to interrupt the program (using <kbd class="kbd docutils literal notranslate">Control-C</kbd> or
whatever the operating system supports); note that a user-generated interruption
is signalled by raising the <a class="reference internal" href="../library/exceptions.html#KeyboardInterrupt" title="KeyboardInterrupt"><code class="xref py py-exc docutils literal notranslate">KeyboardInterrupt</code></a> exception.
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; while True:
... try:
... x = int(input(&quot;Please enter a number: &quot;))
... break
... except ValueError:
... print(&quot;Oops! That was no valid number. Try again...&quot;)
...
</pre></div>
</div>
The <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statement works as follows.
<ul class="simple">
<li>First, the try clause (the statement(s) between the <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> and
<a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> keywords) is executed.</li>
<li>If no exception occurs, the except clause is skipped and execution of the
<a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statement is finished.</li>
<li>If an exception occurs during execution of the try clause, the rest of the
clause is skipped. Then if its type matches the exception named after the
<a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> keyword, the except clause is executed, and then execution
continues after the <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statement.</li>
<li>If an exception occurs which does not match the exception named in the except
clause, it is passed on to outer <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statements; if no handler is
found, it is an unhandled exception and execution stops with a message as
shown above.</li>
</ul>
A <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statement may have more than one except clause, to specify
handlers for different exceptions. At most one handler will be executed.
Handlers only handle exceptions that occur in the corresponding try clause, not
in other handlers of the same <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statement. An except clause may
name multiple exceptions as a parenthesized tuple, for example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>... except (RuntimeError, TypeError, NameError):
... pass
</pre></div>
</div>
A class in an <a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> clause is compatible with an exception if it is
the same class or a base class thereof (but not the other way around — an
except clause listing a derived class is not compatible with a base class). For
example, the following code will print B, C, D in that order:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>class B(Exception):
 pass

class C(B):
 pass

class D(C):
 pass

for cls in [B, C, D]:
 try:
 raise cls()
 except D:
 print(&quot;D&quot;)
 except C:
 print(&quot;C&quot;)
 except B:
 print(&quot;B&quot;)
</pre></div>
</div>
Note that if the except clauses were reversed (with <code class="docutils literal notranslate">except B</code> first), it
would have printed B, B, B — the first matching except clause is triggered.
The last except clause may omit the exception name(s), to serve as a wildcard.
Use this with extreme caution, since it is easy to mask a real programming error
in this way! It can also be used to print an error message and then re-raise
the exception (allowing a caller to handle the exception as well):
<div class="highlight-python3 notranslate"><div class="highlight"><pre>import sys

try:
 f = open(&#39;myfile.txt&#39;)
 s = f.readline()
 i = int(s.strip())
except OSError as err:
 print(&quot;OS error: {0}&quot;.format(err))
except ValueError:
 print(&quot;Could not convert data to an integer.&quot;)
except:
 print(&quot;Unexpected error:&quot;, sys.exc_info()[0])
 raise
</pre></div>
</div>
The <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> … <a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> statement has an optional else
clause, which, when present, must follow all except clauses. It is useful for
code that must be executed if the try clause does not raise an exception. For
example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>for arg in sys.argv[1:]:
 try:
 f = open(arg, &#39;r&#39;)
 except OSError:
 print(&#39;cannot open&#39;, arg)
 else:
 print(arg, &#39;has&#39;, len(f.readlines()), &#39;lines&#39;)
 f.close()
</pre></div>
</div>
The use of the <a class="reference internal" href="../reference/compound_stmts.html#else"><code class="xref std std-keyword docutils literal notranslate">else</code></a> clause is better than adding additional code to
the <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> clause because it avoids accidentally catching an exception
that wasn’t raised by the code being protected by the <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> …
<a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> statement.
When an exception occurs, it may have an associated value, also known as the
exception’s argument. The presence and type of the argument depend on the
exception type.
The except clause may specify a variable after the exception name. The
variable is bound to an exception instance with the arguments stored in
<code class="docutils literal notranslate">instance.args</code>. For convenience, the exception instance defines
<a class="reference internal" href="../reference/datamodel.html#object.__str__" title="object.__str__"><code class="xref py py-meth docutils literal notranslate">__str__()</code></a> so the arguments can be printed directly without having to
reference <code class="docutils literal notranslate">.args</code>. One may also instantiate an exception first before
raising it and add any attributes to it as desired.
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; try:
... raise Exception(&#39;spam&#39;, &#39;eggs&#39;)
... except Exception as inst:
... print(type(inst)) # the exception instance
... print(inst.args) # arguments stored in .args
... print(inst) # __str__ allows args to be printed directly,
... # but may be overridden in exception subclasses
... x, y = inst.args # unpack args
... print(&#39;x =&#39;, x)
... print(&#39;y =&#39;, y)
...
&lt;class &#39;Exception&#39;&gt;
(&#39;spam&#39;, &#39;eggs&#39;)
(&#39;spam&#39;, &#39;eggs&#39;)
x = spam
y = eggs
</pre></div>
</div>
If an exception has arguments, they are printed as the last part (‘detail’) of
the message for unhandled exceptions.
Exception handlers don’t just handle exceptions if they occur immediately in the
try clause, but also if they occur inside functions that are called (even
indirectly) in the try clause. For example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; def this_fails():
... x = 1/0
...
&gt;&gt;&gt; try:
... this_fails()
... except ZeroDivisionError as err:
... print(&#39;Handling run-time error:&#39;, err)
...
Handling run-time error: division by zero
</pre></div>
</div>
</div>
<div class="section" id="raising-exceptions">
<h2>8.4. Raising Exceptions<a class="headerlink" href="#raising-exceptions" title="Permalink to this headline">¶</a></h2>
The <a class="reference internal" href="../reference/simple_stmts.html#raise"><code class="xref std std-keyword docutils literal notranslate">raise</code></a> statement allows the programmer to force a specified
exception to occur. For example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; raise NameError(&#39;HiThere&#39;)
Traceback (most recent call last):
 File &quot;&lt;stdin&gt;&quot;, line 1, in &lt;module&gt;
NameError: HiThere
</pre></div>
</div>
The sole argument to <a class="reference internal" href="../reference/simple_stmts.html#raise"><code class="xref std std-keyword docutils literal notranslate">raise</code></a> indicates the exception to be raised.
This must be either an exception instance or an exception class (a class that
derives from <a class="reference internal" href="../library/exceptions.html#Exception" title="Exception"><code class="xref py py-class docutils literal notranslate">Exception</code></a>). If an exception class is passed, it will
be implicitly instantiated by calling its constructor with no arguments:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>raise ValueError # shorthand for &#39;raise ValueError()&#39;
</pre></div>
</div>
If you need to determine whether an exception was raised but don’t intend to
handle it, a simpler form of the <a class="reference internal" href="../reference/simple_stmts.html#raise"><code class="xref std std-keyword docutils literal notranslate">raise</code></a> statement allows you to
re-raise the exception:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; try:
... raise NameError(&#39;HiThere&#39;)
... except NameError:
... print(&#39;An exception flew by!&#39;)
... raise
...
An exception flew by!
Traceback (most recent call last):
 File &quot;&lt;stdin&gt;&quot;, line 2, in &lt;module&gt;
NameError: HiThere
</pre></div>
</div>
</div>
<div class="section" id="user-defined-exceptions">
<h2>8.5. User-defined Exceptions<a class="headerlink" href="#user-defined-exceptions" title="Permalink to this headline">¶</a></h2>
Programs may name their own exceptions by creating a new exception class (see
<a class="reference internal" href="classes.html#tut-classes">Classes</a> for more about Python classes). Exceptions should typically
be derived from the <a class="reference internal" href="../library/exceptions.html#Exception" title="Exception"><code class="xref py py-exc docutils literal notranslate">Exception</code></a> class, either directly or indirectly.
Exception classes can be defined which do anything any other class can do, but
are usually kept simple, often only offering a number of attributes that allow
information about the error to be extracted by handlers for the exception. When
creating a module that can raise several distinct errors, a common practice is
to create a base class for exceptions defined by that module, and subclass that
to create specific exception classes for different error conditions:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>class Error(Exception):
 &quot;&quot;&quot;Base class for exceptions in this module.&quot;&quot;&quot;
 pass

class InputError(Error):
 &quot;&quot;&quot;Exception raised for errors in the input.

Attributes:
 expression -- input expression in which the error occurred
 message -- explanation of the error
 &quot;&quot;&quot;

def __init__(self, expression, message):
 self.expression = expression
 self.message = message

class TransitionError(Error):
 &quot;&quot;&quot;Raised when an operation attempts a state transition that&#39;s not
 allowed.

Attributes:
 previous -- state at beginning of transition
 next -- attempted new state
 message -- explanation of why the specific transition is not allowed
 &quot;&quot;&quot;

def __init__(self, previous, next, message):
 self.previous = previous
 self.next = next
 self.message = message
</pre></div>
</div>
Most exceptions are defined with names that end in “Error,” similar to the
naming of the standard exceptions.
Many standard modules define their own exceptions to report errors that may
occur in functions they define. More information on classes is presented in
chapter <a class="reference internal" href="classes.html#tut-classes">Classes</a>.
</div>
<div class="section" id="defining-clean-up-actions">
<h2>8.6. Defining Clean-up Actions<a class="headerlink" href="#defining-clean-up-actions" title="Permalink to this headline">¶</a></h2>
The <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statement has another optional clause which is intended to
define clean-up actions that must be executed under all circumstances. For
example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; try:
... raise KeyboardInterrupt
... finally:
... print(&#39;Goodbye, world!&#39;)
...
Goodbye, world!
KeyboardInterrupt
Traceback (most recent call last):
 File &quot;&lt;stdin&gt;&quot;, line 2, in &lt;module&gt;
</pre></div>
</div>
A finally clause is always executed before leaving the <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a>
statement, whether an exception has occurred or not. When an exception has
occurred in the <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> clause and has not been handled by an
<a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> clause (or it has occurred in an <a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> or
<a class="reference internal" href="../reference/compound_stmts.html#else"><code class="xref std std-keyword docutils literal notranslate">else</code></a> clause), it is re-raised after the <a class="reference internal" href="../reference/compound_stmts.html#finally"><code class="xref std std-keyword docutils literal notranslate">finally</code></a> clause has
been executed. The <a class="reference internal" href="../reference/compound_stmts.html#finally"><code class="xref std std-keyword docutils literal notranslate">finally</code></a> clause is also executed “on the way out”
when any other clause of the <a class="reference internal" href="../reference/compound_stmts.html#try"><code class="xref std std-keyword docutils literal notranslate">try</code></a> statement is left via a
<a class="reference internal" href="../reference/simple_stmts.html#break"><code class="xref std std-keyword docutils literal notranslate">break</code></a>, <a class="reference internal" href="../reference/simple_stmts.html#continue"><code class="xref std std-keyword docutils literal notranslate">continue</code></a> or <a class="reference internal" href="../reference/simple_stmts.html#return"><code class="xref std std-keyword docutils literal notranslate">return</code></a> statement. A more
complicated example:
<div class="highlight-python3 notranslate"><div class="highlight"><pre>&gt;&gt;&gt; def divide(x, y):
... try:
... result = x / y
... except ZeroDivisionError:
... print(&quot;division by zero!&quot;)
... else:
... print(&quot;result is&quot;, result)
... finally:
... print(&quot;executing finally clause&quot;)
...
&gt;&gt;&gt; divide(2, 1)
result is 2.0
executing finally clause
&gt;&gt;&gt; divide(2, 0)
division by zero!
executing finally clause
&gt;&gt;&gt; divide(&quot;2&quot;, &quot;1&quot;)
executing finally clause
Traceback (most recent call last):
 File &quot;&lt;stdin&gt;&quot;, line 1, in &lt;module&gt;
 File &quot;&lt;stdin&gt;&quot;, line 3, in divide
TypeError: unsupported operand type(s) for /: &#39;str&#39; and &#39;str&#39;
</pre></div>
</div>
As you can see, the <a class="reference internal" href="../reference/compound_stmts.html#finally"><code class="xref std std-keyword docutils literal notranslate">finally</code></a> clause is executed in any event. The
<a class="reference internal" href="../library/exceptions.html#TypeError" title="TypeError"><code class="xref py py-exc docutils literal notranslate">TypeError</code></a> raised by dividing two strings is not handled by the
<a class="reference internal" href="../reference/compound_stmts.html#except"><code class="xref std std-keyword docutils literal notranslate">except</code></a> clause and therefore re-raised after the <a class="reference internal" href="../reference/compound_stmts.html#finally"><code class="xref std std-keyword docutils literal notranslate">finally</code></a>
clause has been executed.
In real world applications, the <a class="reference internal" href="../reference/compound_stmts.html#finally"><code class="xref std std-keyword docutils literal notranslate">finally</code></a> clause is useful for
releasing external resources (such as files or network connections), regardless
of whether the use of the resource was successful.
</div>
<div class="section" id="predefined-clean-up-actions">
<h2>8.7. Predefined Clean-up Actions<a class="headerlink" href="#predefined-clean-up-actions" title="Permalink to this headline">¶</a></h2>
Some objects define standard clean-up actions to be undertaken when the object
is no longer needed, regardless of whether or not the operation using the object
succeeded or failed. Look at the following example, which tries to open a file
and print its contents to the screen.
<div class="highlight-python3 notranslate"><div class="highlight"><pre>for line in open(&quot;myfile.txt&quot;):
 print(line, end=&quot;&quot;)
</pre></div>
</div>
The problem with this code is that it leaves the file open for an indeterminate
amount of time after this part of the code has finished executing.
This is not an issue in simple scripts, but can be a problem for larger
applications. The <a class="reference internal" href="../reference/compound_stmts.html#with"><code class="xref std std-keyword docutils literal notranslate">with</code></a> statement allows objects like files to be
used in a way that ensures they are always cleaned up promptly and correctly.
<div class="highlight-python3 notranslate"><div class="highlight"><pre>with open(&quot;myfile.txt&quot;) as f:
 for line in f:
 print(line, end=&quot;&quot;)
</pre></div>
</div>
After the statement is executed, the file f is always closed, even if a
problem was encountered while processing the lines. Objects which, like files,
provide predefined clean-up actions will indicate this in their documentation.
</div>
</div>

</div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <h3><a href="../contents.html">Table Of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">8. Errors and Exceptions</a><ul>
<li><a class="reference internal" href="#syntax-errors">8.1. Syntax Errors</a></li>
<li><a class="reference internal" href="#exceptions">8.2. Exceptions</a></li>
<li><a class="reference internal" href="#handling-exceptions">8.3. Handling Exceptions</a></li>
<li><a class="reference internal" href="#raising-exceptions">8.4. Raising Exceptions</a></li>
<li><a class="reference internal" href="#user-defined-exceptions">8.5. User-defined Exceptions</a></li>
<li><a class="reference internal" href="#defining-clean-up-actions">8.6. Defining Clean-up Actions</a></li>
<li><a class="reference internal" href="#predefined-clean-up-actions">8.7. Predefined Clean-up Actions</a></li>
</ul>
</li>
</ul>

<h4>Previous topic</h4>
 <a href="inputoutput.html"
 title="previous chapter">7. Input and Output</a>
 <h4>Next topic</h4>
 <a href="classes.html"
 title="next chapter">9. Classes</a>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li>
 <a href="https://github.com/python/cpython/blob/3.6/Doc/tutorial/errors.rst"
 rel="nofollow">Show Source
 </a>
 </li>
 </ul>
 </div>
 </div>
 </div>
 <div class="clearer"></div>
 </div> 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="classes.html" title="9. Classes"
 >next</a> |</li>
 <li class="right" >
 <a href="inputoutput.html" title="7. Input and Output"
 >previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li>
 <a href="../index.html">3.6.7 Documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" >The Python Tutorial</a> &#187;</li>
 <li class="right">

</ul>
 </div> 
 <div class="footer">
 &copy; <a href="../copyright.html">Copyright</a> 2001-2023, Python Software Foundation.
 
 The Python Software Foundation is a non-profit corporation.
 <a href="https://www.python.org/psf/donations/">Please donate.</a>
 
 Last updated on Dec 18, 2023.
 <a href="../bugs.html">Found a bug</a>?
 
 Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.7.6.
 </div>

</body>
</html>

CANCEL

Name	Type	Size	Modified	Actions
↩ ..	DIR	—	—
📄 appendix.html	HTML	17.3 KB	2023-12-18 11:36	EDIT
📄 appetite.html	HTML	11.1 KB	2023-12-18 11:36	EDIT
📄 classes.html	HTML	90.1 KB	2023-12-18 11:36	EDIT
📄 controlflow.html	HTML	83.8 KB	2023-12-18 11:36	EDIT
📄 datastructures.html	HTML	82.7 KB	2023-12-18 11:36	EDIT
📄 errors.html	HTML	47.3 KB	2023-12-18 11:36	EDIT
📄 floatingpoint.html	HTML	31.8 KB	2023-12-18 11:36	EDIT
📄 index.html	HTML	25.9 KB	2023-12-18 11:36	EDIT
📄 inputoutput.html	HTML	56.2 KB	2023-12-18 11:36	EDIT
📄 interactive.html	HTML	10.4 KB	2023-12-18 11:36	EDIT
📄 interpreter.html	HTML	19.9 KB	2023-12-18 11:36	EDIT
📄 introduction.html	HTML	57.8 KB	2023-12-18 11:36	EDIT
📄 modules.html	HTML	58.5 KB	2023-12-18 11:36	EDIT
📄 stdlib.html	HTML	46.5 KB	2023-12-18 11:36	EDIT
📄 stdlib2.html	HTML	56.3 KB	2023-12-18 11:36	EDIT
📄 venv.html	HTML	21.3 KB	2023-12-18 11:36	EDIT
📄 whatnow.html	HTML	11.1 KB	2023-12-18 11:36	EDIT