CH07.03: Programming With Exceptions

DuckTales: Debugging the Duck-o-Tron 3000

Gyro Gearloose is at it again with the Duck-o-Tron 3000, a gadget buzzing with adventure potential—if it doesn’t short-circuit first! The Duck kids are hyped to test it, but Gyro’s demo is tomorrow, and errors are popping up like Beagle Boys at a bank heist.

Your mission:
- - use try/except to debug this tech and make it shine.
  - Pick your tier—Rookie, Tinkerer, or Master—and let’s get this gizmo quacking! 🦆✨

Objective:

Craft a Python program to configure and test the Duck-o-Tron 3000.
Use functions and try/except to squash errors, and format output with clean spacing, underlines, and a dash of emoji magic. 🚀

Program Requirements

Base Setup (All Tiers)

Use functions for each task (e.g., set_speed(), pick_pilot()).
Apply exception handling with try/except to keep it running.
Add a DuckTales character’s funny quip for invalid input (e.g., Gyro, Launchpad).
Add formatting, emojis, and other things to make your output slick!

End-of-Run Report Card

Your program, no matter what level you're programming, must have an end of run report card that shows all important stats!

Tier 1: Rookie Inventor (Beginner)

“Aw, phooey!” Dewey grumbles as the Duck-o-Tron 3000 coughs smoke on the launchpad. “We’ve gotta get this thing flying before Gyro’s demo—or Uncle Scrooge turns it into a paperweight!” Your job: set the flight speed and pick a pilot to take it for a spin. Launchpad’s eager to soar, but he’s clueless with numbers—don’t let him crash it with bad input! Huey’s ready with his guidebook to yell tips when you goof. Can you launch this test flight? 🛫

Requirements:

Ask for flight speed (a number)
- Catch All ValueError (non-numbers)
Print and Select possible pilots
- Catch ValueError (non-numbers)
- Catch IndexError (out-of-range)
Loop until valid input and print error message prompting the user to re-enter a valid value
Show a clean output with underlines and emojis.

Tier 2: Gadget Tinkerer (Intermediate)

“Great blazing bulbs!” Gyro yelps, pacing the lab in a panic. “Launchpad’s gonna smash this thing to bits unless we test its durability!” Your mission: set the flight speed and pilot, then run the Duck-o-Tron through a crash simulator. Huey’s adamant the crash count stays sane (1-10), and Louie’s fretting over the gadget’s base durability—don’t let it flop with bad math! Can you toughen this tech for the big show? 💪

Requirements:

Include Tier 1 tasks (speed and pilot).
Ask for crash test count (1-10) under a header
Catch ValueError and enforce 1-10 range. Loop until valid.
- If there's an error, print a message:
  - “Great Scott! Keep it 1-10, or this thing’s scrap metal! 🔥”
Ask for base durability:
- Catch ValueError
- Calculate Score:
  - score = base_durability / crash_tests
  - Catch ValueError

Tier 3: Master Engineer (Advanced)

“Eureka!” Gyro cheers, goggles steaming with glee. “The Duck-o-Tron 3000’s almost flawless, but it needs a mission code and activation key to unlock its true power!” Webby’s dreaming up a snazzy code name (letters only!), while Louie’s plotting a numeric key—keep ‘em straight! Then, test startup stress by dividing durability by the key. If it’s zero, the gadget fizzles, and Gyro’s demo’s kaput. Can you master this machine? 🎯

Requirements:

Include Tier 2 tasks (speed, pilot, durability).
Ask for mission code (letters only)
- Catch non-letters with a custom check. Loop until valid.
Ask for activation key (numbers only):
- Catch non-numbers and ZeroDivisionError (if 0). Loop until valid.
Calculate stress = durability_score / activation_key.
Show a deluxe report with underlines and emojis.

Tier 4: Gizmo-Duck Level

🛠️ Damage System

Instead of one durability score, let crashes reduce durability step-by-step.
Example:
- - Start durability = 100
  - Each crash:
    - - Random damage (5–20)
  - Print status after each crash
  - If durability hits 0 → FAIL STATE

Page updated

Report abuse