Production checklist

Shipping Python means pinned dependencies, venv or containers, logging instead of bare print(), tests in CI, and type checking—not just "works on my laptop."

Checklist

• Pin dependencies in requirements.txt or pyproject.toml
• Use venv or Docker for reproducible environments
• Run pytest and optionally mypy in CI
• Use the logging module in services—not print in production
• Handle secrets via environment variables, never commit .env
• Web concerns (ORM, auth, deployment) live in the Django track

Important interview questions and answers

1. Q: Why pin pip versions?
   A: Reproducible builds—surprise upgrades break CI and production deploys.
2. Q: logging vs print?
   A: Logging supports levels, handlers, and structured output for observability; print is for dev debugging.

Self-check

1. What file pins Python package versions?
2. Why separate language track from Django track?
3. Name the test runner used in this curriculum.

Track summary

You covered Python language fundamentals: syntax, data structures, OOP, stdlib modules, modern features, tooling, and interview context. Continue with local venv projects and advance to the Django track for HTTP, ORM, and deployment—or compare patterns with JavaScript, Java, and C# tracks.

Next steps

1. Create a venv project with pytest and type hints locally
2. Practice exercism.org or Advent of Code in Python
3. Build a CLI tool using argparse and pathlib
4. Advance to Django for web backends

Tip: Use logging not print in production—this lesson closes the track; next stop: Django.