Challenge 2: Never Having Used venv/pip Outside PyCharm — Solution Walkthrough

The risk this student is facing:

Per this chapter's own warning box, PyCharm's own virtual environment
UI is a convenience layer over the same underlying venv/pip/conda
tools — it doesn't replace needing to understand what those tools
actually do. Having only ever clicked through PyCharm's own UI means
this student has no practical experience actually running venv or
pip directly from a terminal, which is exactly what setting up the
environment on a production server with no PyCharm installed will
require.

Why this specific situation exposes the gap:

The production server has no PyCharm UI to click through at all — it
only understands the underlying command-line tools directly. Without
knowing how to create a virtual environment with venv, activate it,
and install the correct dependencies with pip from the command line,
this student has no path to reproducing their project's environment
on that server, even though they've successfully done the equivalent
task inside PyCharm many times.

What this chapter's warning box specifically anticipated:

This is precisely the risk named in this chapter's own warning box —
"not knowing how to reproduce the same environment outside PyCharm
entirely, for instance on a deployment server that has no PyCharm
installed at all."

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies this chapter's own warning box to the
exact scenario it was written to describe, correctly identifying the
gap between GUI-only familiarity and the underlying command-line
skill actually needed outside the IDE.