Skip to Content
Python Intermediate: Write Code You Won't Be Embarrassed to Share
Intermediate
0 likes
Courses
Python Intermediate: Write Code You Won't Be Embarrassed to Share

Final Check: Python Intermediate

Fifteen questions across the whole course: environments, project structure, classes, files, comprehensions, testing and debugging. If you pass this, you can work on a shared Python project without being the person everybody has to clean up after.

15 min PythonObject-Oriented ProgrammingTesting and DebuggingAutomation and ScriptingPackaging and Dependencies Intermediate
Prev Next
Fullscreen Share
Course content

Sign in to save your progress.

Course Home
1. You start a new project that needs a different version of a library than your other projects. What is the first step?
Create a virtual environment for the new project and install into it with python -m pip. Install the new version globally and hope the old projects still work. Uninstall Python and reinstall it.
2. A new teammate cloned the repository and asks how to get the same packages you have. What do you tell them?
Copy my .venv folder. Create a .venv and run python -m pip install -r requirements.txt. Install packages as error messages ask for them.
3. Your 1,500-line script has price rules, file reading and email sending mixed together. What is a sensible first step?
Split it into utils1.py, utils2.py and utils3.py by line count. Move related functions into modules named after what they do, like pricing.py and storage.py, and keep main.py short. Leave it. Splitting never helps.
4. Running python shop/orders.py gives "attempted relative import with no known parent package". What is going on?
The shop package is corrupted. The file uses a relative import like from .pricing import add_vat, which only works when it runs as part of the package, for example python -m shop.orders. Relative imports were removed in Python 3.
5. You need an order object with items, a status, and the rule "no new items after payment". What is the best fit?
A dictionary, checked by each function that uses it. A class with an add_item method that checks the status. A global variable for each order.
6. You want a small class that only holds a product's name, price and stock, with a readable print and == comparison. What saves the most typing?
A regular class with a hand-written __init__, __repr__ and __eq__. @dataclass A tuple
7. Your script crashed halfway while writing report.csv with "w". What does the next program that reads report.csv see?
The old report, untouched. A partly written file, because "w" erased the old content before writing started. An error saying the file is incomplete.
8. You need every .csv file in a folder and all its subfolders. Which is right?
Path("inbox").glob("*.csv") Path("inbox").rglob("*.csv") os.listdir("inbox") with a string check
9. A date column has "10/03/2026". Your cleaning function expects YYYY-MM-DD. What should it do?
Guess October 3, since that is the most common format. Reject the row with a clear reason, so it gets fixed at the source. Store it as text and move on.
10. What does {e.strip().lower() for e in emails} produce?
A list with every email lowercased. A set of unique, cleaned email addresses. A dictionary of emails.
11. A comprehension has two nested for parts, three conditions and needs a line break to fit. What does the course recommend?
Keep it. Fewer lines are always better. Move the condition into a named function, or write a plain loop. Use the walrus operator to fit more in.
12. When should a function's tests include the exact limit, like 1,000 for free shipping?
Always, when there is a limit. That is where off-by-one bugs live. Only if a customer has already complained. Never. Testing far away from the limit is enough.
13. Which logging setup belongs in a module that other scripts import?
logging.basicConfig(level=logging.DEBUG) at the top of the module. log = logging.getLogger(__name__), with logging configured once in the main script. print() with "DEBUG:" in front.
14. Which of these should never appear in a log file?
The ID of the order that failed. A customer's full card number or a password. The name of the function that failed.
15. You found the cause of a bug. What should you do before fixing it?
Nothing. Fix it as fast as possible. Write a test that fails because of the bug, then fix it, so it can't quietly return. Add a comment saying the bug was fixed.

About

Fifteen questions across the whole course: environments, project structure, classes, files, comprehensions, testing and debugging. If you pass this, you can work on a shared Python project without being the person everybody has to clean up after.

Duration
15 min
Last update
09/14/2026
Was this helpful?
​ 0 ​ 0

Comments (0)

Sign in to comment

No comments yet.