This section has covered core Python — the part that stays the same no matter which of the domains from the first lesson you go on to work in. This closing lesson covers one practical workflow habit, and points toward what comes next.
Different projects often need different, sometimes conflicting, versions of the same package. A virtual environment gives each project its own isolated set of installed packages, instead of one shared pile for your entire machine:
python3 -m venv myproject-env # create it, once per project
source myproject-env/bin/activate # activate it (Windows: myproject-env\Scripts\activate)
pip install requests # installs only into this project's environment
deactivate # done for nowDo this from your very first real project
Real Python projects create a virtual environment as one of the very first steps, before installing anything with pip. It's not a language feature, just a strong, near-universal convention — worth building the habit early.
| If you want to... | Look at |
|---|---|
| Build web applications | Flask (small, flexible) or Django (larger, more built-in structure) |
| Work with data | pandas (data analysis), NumPy (numerical computing) |
| Do machine learning / AI | scikit-learn, PyTorch, TensorFlow |
| Automate tasks | The standard library alone often covers this — os, shutil, subprocess |
None of these are covered in this section on purpose — each is substantial enough to deserve its own dedicated learning path once core Python feels comfortable, and picking one before you're ready to use it well tends to slow learning down rather than speed it up.
This section can't track every detail of a language that keeps evolving. The official Python documentation is the authoritative, always-current reference — worth bookmarking, and worth reaching for whenever you need something more exhaustive than a lesson here provides.
The fundamentals in this section — data types, control flow, functions, OOP, files, and databases — are the same whichever direction you take from here.