GeezerVison is showing github.com — learn-python/src/exceptions/test_handle_exceptions.py at master · devarajthiyam/learn-python

Expand file tree

test_handle_exceptions.py

Copy path

More file actions

Latest commit

History

106 lines (83 loc) · 3.8 KB

test_handle_exceptions.py

Copy path

File metadata and controls

106 lines (83 loc) · 3.8 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

100

101

102

103

104

105

106

"""Errors and Exceptions.

@see: https://docs.python.org/3/tutorial/errors.html#errors-and-exceptions

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.

It is possible to write programs that handle selected exceptions.

"""

def test_handle_exceptions():

"""Handling of exceptions

The try statement works as follows.

- First, the try clause (the statement(s) between the try and except keywords) is executed.

- If no exception occurs, the except clause is skipped and execution of the try statement

is finished.

- 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 except keyword, the except clause is

executed, and then execution continues after the try statement.

- If an exception occurs which does not match the exception named in the except clause, it is

passed on to outer try statements; if no handler is found, it is an unhandled exception and

execution stops with a message.

"""

# Let's simulate division by zero exception.

exception_has_been_handled = False

try:

result = 10 * (1 / 0) # division by zero

# We should not get here at all.

assert result

except ZeroDivisionError:

# We should get here because of division by zero.

exception_has_been_handled = True

assert exception_has_been_handled

# Let's simulate undefined variable access exception.

exception_has_been_handled = False

try:

# pylint: disable=undefined-variable

result = 4 + spam * 3 # name 'spam' is not defined

# We should not get here at all.

assert result

except NameError:

# We should get here because of division by zero.

exception_has_been_handled = True

assert exception_has_been_handled

# A try 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 try statement. An except

# clause may name multiple exceptions as a parenthesized tuple, for example:

exception_has_been_handled = False

try:

result = 10 * (1 / 0) # division by zero

# We should not get here at all.

assert result

except (ZeroDivisionError, NameError):

# We should get here because of division by zero.

exception_has_been_handled = True

assert exception_has_been_handled

# Exception handlers may be chained.

exception_has_been_handled = False

try:

result = 10 * (1 / 0) # division by zero

# We should not get here at all.

assert result

except NameError:

# We should get here because of division by zero.

exception_has_been_handled = True

except ZeroDivisionError:

# We should get here because of division by zero.

exception_has_been_handled = True

assert exception_has_been_handled

# The try … except 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:

exception_has_been_handled = False

no_exceptions_has_been_fired = False

try:

result = 10

# We should not get here at all.

assert result

except NameError:

# We should get here because of division by zero.

exception_has_been_handled = True

else:

no_exceptions_has_been_fired = True

assert not exception_has_been_handled

assert no_exceptions_has_been_fired