Level 3 exam — Python · GUIDINEE.COM

Exam — fresh questions

12 questions to validate intermediate Python: modules and stdlib, venv and pip, decorators and generators, pytest and hints.
Answer everything, then click Check: your score and explanations will appear.

3.1 · Recall

1. A module and a package are…

A computer keyboard and screen A reusable .py file and a folder of modules A main course and a dessert A printer and its paper

Module = .py file; package = folder — both are imported instead of copied.

3.1 · Application

2. Nabil reuses frequence from stats.py without replaying the demo. He writes…

from stats import * everywhere Taking a photo of the demo from stats import frequence + demo under if __name__ == "__main__" Copying the function into each script

Explicit import + demo under __main__: imported = functions only.

3.1 · Arbitration

3. A colleague suggests from utils import * “to go fast”. Correct call?

Delete all project imports Refuse: explicit, absolute imports, never a star Accept, the star is always safe Print the module to check by eye

The star pollutes the namespace and hides origins — explicit and absolute, no exceptions.

3.2 · Recall

4. A venv's job is first to…

Hide code from colleagues Speed up the office printer Change the machine's wallpaper Isolate a project's dependencies to avoid conflicts

One Python + packages per project: two incompatible versions coexist undisturbed.

3.2 · Application

5. Nabil isolates his sales analysis then pins the contract. He writes…

python -m venv .venv, activate, pip install requests, pip freeze > requirements.txt Install everything globally with no venv Commit the .venv folder to Git Note versions on a sticky note

Create, activate, install, pin: versioned requirements makes the project portable.

3.2 · Arbitration

6. Should the .venv folder be versioned? Correct call?

Yes, with passwords inside Yes, printed and bound each month No: ignore .venv, version requirements.txt, rebuild with install -r Neither, all from memory

.venv = bulky and machine-specific; requirements alone rebuilds.

3.3 · Application

7. Nabil sorts his sales by amount in one throwaway line. He writes…

Switch the machine off and on again sorted(ventes, key=lambda v: v["montant"]) Sort by hand on paper sorted(ventes) with no criterion, hoping

Throwaway lambda in key: one-line criterion, def as soon as it gets a name.

3.3 · Application

8. Nabil reads a multi-GB export without saturating RAM. He writes…

A full printout of the export A giant list loaded at once A generator with yield line by line A copy-paste of the file ten times over

Yield produces on demand: constant memory, even over GBs.

3.3 · Recall

9. A decorator with functools.wraps is for…

Deleting the decorated function Changing the terminal font Packing the machine for transport Enriching a function without touching its code, keeping name and doc

It receives the function, returns a wrapper (timer, log) — wraps preserves identity.

3.4 · Application

10. Nabil tests his VAT: nominal and negative price. He writes…

assert tva(100) == 120 + with pytest.raises(ValueError): tva(-5) A “should work” comment A single print thrown away after use No test, we will see in production

Minimal trio: nominal + edge + error — pytest -q after each change.

3.4 · Application

11. Nabil documents his average function without changing execution. He writes…

A hardcoded password in the code A screenshot of the function A poem about averages in Algiers def moyenne(notes: list[float]) -> float: …

Hints = readable intent, ignored at runtime, checkable by mypy.

3.4 · Arbitration

12. Before sending reports, Nabil only tested the nominal case. Correct call?

Add edges + errors (empty, negative) and rerun pytest before sending Delete tests to go faster Print reports to check by eye Send anyway, nominal is enough

Bugs live at the edges: with no edges or errors, regressions go unnoticed.

What's next?

Score ≥ 80%: move to Level 4 — Django, Flask/FastAPI APIs and pandas data (building on proven foundations).
Score 50-79%: revisit the failed sections (modules in 3.1, venv in 3.2, decorators/yield in 3.3, pytest/hints in 3.4) then retake the test.
Score < 50%: reread level 2 (structures, files, errors) then replay each 48h challenge in order.