Try–except–finally behavior in Python - Time & Space Complexity

Time Complexity: Try-except-finally behavior

O(n)

Understanding Time Complexity

We want to understand how the time a program takes changes when using try, except, and finally blocks.

Specifically, we ask: how does adding error handling affect the number of steps the program runs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

def process(items):
    for item in items:
        try:
            print(item / 2)
        except TypeError:
            print("Not a number")
        finally:
            print("Done with item")

This code goes through a list, tries to divide each item by 2, handles errors if the item is not a number, and always prints a message after each item.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each item in the list.
• How many times: Once for each item in the input list.

How Execution Grows With Input

Each item causes a fixed number of steps: try dividing, maybe catch an error, then print a message.

Input Size (n)	Approx. Operations
10	About 30 steps (3 steps per item)
100	About 300 steps
1000	About 3000 steps

Pattern observation: The total steps grow directly with the number of items. Double the items, double the steps.

Final Time Complexity

Time Complexity: O(n)

This means the time grows in a straight line with the number of items processed.

Common Mistake

[X] Wrong: "Try-except-finally blocks make the program much slower and change how time grows with input size."

[OK] Correct: The error handling adds a small fixed cost per item, but the overall time still grows linearly with the number of items.

Interview Connect

Understanding how error handling affects performance helps you write clear and efficient code, a skill valued in real projects and interviews.

Self-Check

"What if the try block contained a nested loop over the items? How would the time complexity change?"

Practice

1. What does the finally block do in a try-except-finally structure?

easy

A. It always runs, whether an error occurs or not.

B. It runs only if an error occurs.

C. It runs only if no error occurs.

D. It runs before the try block.

Solution

1. Step 1: Understand the role of try and except

   The try block runs code that might cause an error, and except runs only if an error happens.

2. Step 2: Understand the finally block behavior

   The finally block always runs after try and except, no matter if an error occurred or not.

3. Final Answer:

   It always runs, whether an error occurs or not. -> Option A

4. Quick Check:

   finally always runs = A [OK]

Hint: Remember: finally always runs last, no matter what. [OK]

Common Mistakes:

• Thinking finally runs only on errors
• Confusing except and finally blocks
• Believing finally runs before try

2. Which of the following is the correct syntax for a try-except-finally block in Python?

easy

A. except:
pass
try:
pass
finally:
pass

B. try:
pass
finally:
pass
except:
pass

C. try:
pass
except:
pass
finally:
pass

D. try:
pass
except:
pass
else:
pass

Solution

1. Step 1: Recall the order of blocks

   The correct order is try, then except, then finally.

2. Step 2: Check each option's order

   try: pass except: pass finally: pass follows the correct order. try: pass finally: pass except: pass places finally before except, which is invalid. except: pass try: pass finally: pass starts with except, which is wrong. try: pass except: pass else: pass uses else but no finally.

3. Final Answer:

   try, except, finally in correct order -> Option C

4. Quick Check:

   try-except-finally order = C [OK]

Hint: Remember order: try, except, then finally. [OK]

Common Mistakes:

• Placing finally before except
• Starting with except block
• Confusing else with finally

3. What will be the output of this code?

try:
    print('Start')
    x = 1 / 0
except ZeroDivisionError:
    print('Error caught')
finally:
    print('Always runs')

medium

A. Start\nAlways runs

B. Start\nError caught

C. Error caught\nAlways runs

D. Start\nError caught\nAlways runs

Solution

1. Step 1: Trace the try block

   The code prints 'Start' then tries to divide by zero, causing a ZeroDivisionError.

2. Step 2: Handle the exception and finally block

   The except block catches the error and prints 'Error caught'. Then the finally block runs and prints 'Always runs'.

3. Final Answer:

   Start\nError caught\nAlways runs -> Option D

4. Quick Check:

   try prints + except prints + finally prints = A [OK]

Hint: finally always prints last, even after except. [OK]

Common Mistakes:

• Forgetting finally runs
• Assuming code stops after error
• Missing the initial print before error

4. Find the error in this code snippet:

try:
    print('Hello')
except:
    print('Error')
finally
    print('Done')

medium

A. Missing colon after except

B. Missing colon after finally

C. Indentation error in try block

D. No error, code is correct

Solution

1. Step 1: Check syntax of try-except-finally

   Each block header must end with a colon (:). The finally line is missing a colon.

2. Step 2: Verify other parts

   The except line has a colon, and indentation is correct.

3. Final Answer:

   Missing colon after finally -> Option B

4. Quick Check:

   Colon needed after finally = B [OK]

Hint: Check colons after try, except, finally lines. [OK]

Common Mistakes:

• Ignoring missing colon errors
• Confusing except and finally syntax
• Assuming indentation fixes missing colon

5. Consider this code:

def test():
    try:
        return 'try'
    except:
        return 'except'
    finally:
        return 'finally'

result = test()
print(result)

What will be printed?

hard

A. finally

B. except

C. None

D. try

Solution

1. Step 1: Understand return in try and finally

   The try block returns 'try', but the finally block also has a return statement.

2. Step 2: Know that finally return overrides others

   In Python, if finally has a return, it overrides any previous return from try or except.

3. Step 3: Determine final output

   The function returns 'finally', so print(result) outputs 'finally'.

4. Final Answer:

   finally -> Option A

5. Quick Check:

   finally return overrides try/except returns = D [OK]

Hint: Return in finally overrides try/except returns. [OK]

Common Mistakes:

• Thinking try return is final
• Ignoring finally's return effect
• Assuming except runs without error