🚑
STUDENT NOTES · DAY 14 OF 24
Error Shields 🛡️
Users type "ten" instead of 10. WiFi dies. Files go missing. Today your programs learn to survive it all.
1Watch a program die 💀
🐞
Bugly: My favourite moment — the user types words where numbers belong:
2The shield: try / except
🐍
Py: try = attempt this. except = if it explodes, do THIS instead of crashing. The program lives on!
3Different shields for different errors
🦉
Professor Hoot: Catch specific errors so each mistake gets the right message. A good program is a good doctor — right diagnosis, right cure.
4finally — the loyal cleanup crew
🤖
Bittu: finally runs NO MATTER WHAT — error or no error. Perfect for cleanup jobs like closing things.
5Quick quiz! 🧠
What error does int("hello") raise?
💡 Right type (a string), impossible VALUE — no number hides inside "hello".
When does the finally block run?
💡 finally is the loyal friend: it shows up no matter how the try ended.
6Your mission 🚀
Mission 1: Ask for the user's age with int(input()). Catch ValueError and reply "Numbers only, boss! 😄".
Mission 2: Build a divider: ask two numbers, divide, and catch ZeroDivisionError with a funny message.
Mission 3: Wrap yesterday's file-reading in try/except FileNotFoundError.
Day 14 done — crash-proof coder! 🛡️
Next: APIs — your code talks to the internet.
Go to Day 15: APIs →