Make Python yours / CORE PATH
Interpreter & virtual environments
Keep each project isolated and make the interpreter explicit.
Use your existing Windows setup. Docker and WSL are optional for this roadmap.
Understand the idea
An environment isolates project dependencies, while the interpreter still has its own version and executable path. Confirm both before installing or upgrading packages.
On your Windows workflow, invoking .venv\Scripts\python.exe directly avoids needing to change activation policy. Keep the environment reproducible rather than copying it between machines.
What to learn
- Inspect the installed interpreter before changing anything.
- Create a project .venv and run Python through its explicit path.
- Keep .venv, secrets and generated files out of Git.
Practice on your own data
Follow docs/setup-windows.md and print sys.executable from the project interpreter.
Practice this lesson in the Python lab →
A fresh terminal runs the tests with the same interpreter, without changing PowerShell policy.
Prerequisites
Start here
Video and playlist companions
Choose one explanation for the concept, then attempt the practice. These are topic mappings, not a claim that every linked lesson covers every outcome.
Python - The Basics - Part 1 | جحر السوعبان
Loads YouTube on request. Open on YouTube ↗ if the owner restricts embedding.
The Complete Guide to Python Virtual Environments!
Loads YouTube on request. Open on YouTube ↗ if the owner restricts embedding.
Sources and further reading
- PyPA · environments & packages ↗Official documentation
- Python language tutorial ↗Official documentation
- Python - The Basics - Part 1 | جحر السوعبان ↗User-selected YouTube resource
- The Complete Guide to Python Virtual Environments! ↗User-selected YouTube resource
Track progress on this topic → · Markdown source ↗