•
Install Python 3, pip, and VS Code on Windows or Mac in one after-work sitting, run a hello file, and fix common PATH mistakes.
You do not need a weekend block to install Python. One quiet evening is enough. This guide covers Python 3, pip, VS Code, and a hello file on Windows and Mac. When the file runs, you can stop. Syntax can wait for the next sitting.
A lot of beginners stall on install. Tutorials jump to lists and loops, then the terminal says python is not found. That is a PATH problem, not a talent problem.
If you study after work in Hong Kong, Taiwan, or elsewhere, you already have a full day behind you. Setup should be a short, finishable job. You want:
pip talking to that same Python.py fileThat is the whole environment. You do not need Anaconda, Docker, or a second machine tonight.
SoloQuant Academy's Introduction to Python Programming starts from this same setup, then walks syntax and first programs with libraries in short lessons. Use this article to get the machine ready. Use the course when you want guided practice.
Office laptops with locked install rights are harder. If IT blocks installers, ask for Python 3 and VS Code, or use a personal machine for study.
Download only from python.org and code.visualstudio.com. Skip random "free Python" ads.
python --version
py --version
python -m pip --version
You want a Python 3.x.x line. If python fails but py works, the Windows launcher is fine. Prefer py -3 and py -3 -m pip until PATH is clean.
If both fail, Python is installed but not on PATH. See the PATH section below. Do not install a second copy on top until you check Apps & Features.
Macs often ship with a python3 stub or an older tool chain. For study, install a current Python 3 from python.org.
python3 --version
python3 -m pip --version
Use python3, not python. On many Macs, python is missing or points at something you do not want.
Homebrew users can run brew install python instead. Either path is fine. Confirm the version after install.
If Terminal still cannot find python3, log out and back in, or open a fresh Terminal tab. Installers update PATH for new sessions, not always for the one that was already open.
pip installs packages (libraries) into a Python. The trap is running pip from one Python and python from another.
Always call pip as a module:
python3 -m pip --version
Windows:
python -m pip --version
The version line should mention the same Python you just tested. That habit avoids "I installed requests but import failed" later.
You do not need extra packages tonight. pip only needs to exist.
Visual Studio Code is enough. It is an editor, not a full IDE you have to learn first.
python-evening on your Desktop.hello.py.You can use another editor. PyCharm Community and other VS Code-based editors work. For a 30-minute evening, VS Code is the shortest path.
Put this in hello.py:
print("Hello, world")
print("Python is running on this machine.")
Save the file.
In VS Code, open the built-in terminal (Terminal → New Terminal). Confirm you are in the folder that contains hello.py.
Mac:
python3 hello.py
Windows:
python hello.py
Expected output:
Hello, world
Python is running on this machine.
If VS Code offers a Python interpreter picker, choose the Python 3 you just installed, not a Store stub or an old 2.x.
That two-line file is a real program. The interpreter read a file and ran it. You now have a working environment.
These are the errors that eat a second evening. Read them once so you can stop quickly.
You skipped "Add to PATH" on Windows.
Symptoms: python is not recognized. Fix: re-run the installer, choose Modify, enable PATH, or add the Python folder and the Scripts folder to User PATH. Then open a new PowerShell.
You mixed python and python3.
On Mac, python3 is the one you want. On Windows, python or py -3. Pick one command and stick to it for the night.
Old terminal session. PATH changes apply to new terminals. Close the tab, open another, try again.
Two Pythons.
Microsoft Store Python, python.org Python, and Anaconda can coexist. Check with where python (Windows) or which -a python3 (Mac). Select the python.org (or Homebrew) 3.x in VS Code.
Typed Python or PYTHON.
The command is lowercase python / python3.
Ran the file by double-clicking. A window may flash and close. Run from the terminal so you can read the output.
Company proxy or missing install rights. The installer never finishes, or Python installs for another user. Use a personal machine if the office PC is locked.
Installing packages globally on night one.
Skip this tonight. When you start libraries, use python -m pip install ... on the same interpreter, and later a virtual environment. The intro course covers that in the setup lesson.
If hello.py prints two lines, you are done. Do not "clean up" by uninstalling and reinstalling unless the version command is still wrong.
Tonight is install and proof. It is not:
Those come later. A working hello.py is the gate.
When you have another evening, learn the language on this same machine.
A useful order:
That is the shape of SoloQuant's intro course: 19 short lessons, written for people who study after work rather than a fixed weekday-evening classroom. You already finished the environment piece this article covers.
Related reading on this hub (when those posts are live): a first program that uses a library, not another print; and how 19 short lessons fit a work week. Until then, start with the course itself.
If you later want data analysis, treat it as a later step. A data-analysis course may appear in the catalog; it is not a live multi-dozen-lesson path today.
You have Python 3, pip, VS Code, and a hello file. That is the setup.
Continue in Introduction to Python Programming — self-paced short lessons from environment through core syntax to first programs with libraries. No commute. No need to finish in one night.
Open the course, do the setup lesson as a check, then stop when you are tired. The interpreter will still be there tomorrow.