Set up Python after work in 30 minutes (Windows, Mac, VS Code)

You do not need a Saturday workshop to install Python. You need a quiet half hour after dinner, a laptop, and a plan that does not wander into ten extra tools.

This guide is for people who work full time. The goal is simple: Python 3, pip, and VS Code on Windows or Mac, then one .py file that actually runs. Tomorrow you can learn syntax. Tonight you only need a working environment.

Why install tonight, not "this weekend"

Weekends fill up. After-work slots are smaller, but they are real. If you wait for a free Saturday, you wait for months.

A working install also removes the first excuse. When a lesson asks you to run a script, you will not spend the evening fighting PATH instead of reading the lesson.

You do not need Anaconda, Docker, or a cloud notebook for this first night. Official Python, pip that ships with it, and VS Code are enough.

What you will have after 30 minutes

• Python 3 from python.org (Windows) or the current installer / Homebrew (Mac)
• python or python3 on your PATH
• pip for packages later
• VS Code with the Python extension
• One file, hello.py, that prints a line and exits cleanly

That is the whole night. No virtualenv yet unless you already know why you want one.

Windows: install Python 3 without PATH surprises

1. Open python.org/downloads and get the latest stable Python 3 for Windows.
2. Run the installer.
3. Check "Add python.exe to PATH" before you click Install. This is the mistake that costs people a second evening.
4. Choose "Install Now" unless you have a reason to pick a custom folder.
5. When it finishes, open Command Prompt and run:

python --version
pip --version

You should see a 3.x version. If python is not recognized, close the terminal, open a new one, and try again. Installers change PATH for new sessions only.

If it still fails, search Windows for "Manage app execution aliases" and turn off the App Installer aliases for python.exe and python3.exe. Those stubs look like Python and then do nothing useful.

Re-run the installer, choose Modify, and confirm PATH is enabled.

Mac: install Python 3 you can actually call

macOS often already has a python3 binary. Do not assume it is the one you want, and do not replace system files.

Two honest options:

Option A — python.org installer. Download the macOS installer from python.org, run it, then open Terminal:

python3 --version
pip3 --version

Option B — Homebrew, if you already use it:

brew install python
python3 --version
pip3 --version

On Mac, prefer python3 and pip3 so you do not collide with any leftover python name. If python3 is missing, the installer did not finish or you need a new Terminal window.

Do not spend tonight on pyenv unless you already live in that toolchain.

Confirm pip before you open the editor

pip is how you will install libraries later. You do not need a library tonight, but you need pip to answer.

Windows:

python -m pip --version

Mac:

python3 -m pip --version

The -m pip form is the reliable one. It uses the same interpreter you just installed, not some other pip hiding on PATH.

If this command fails, your Python install is incomplete. Fix that before VS Code. An editor cannot repair a missing interpreter.

Install VS Code and the Python extension

1. Download VS Code from code.visualstudio.com.
2. Install it like any other app.
3. Open VS Code, open Extensions, search for Python (the one from Microsoft), and install it.
4. Command Palette (Ctrl+Shift+P or Cmd+Shift+P) → Python: Select Interpreter.
5. Pick the 3.x interpreter you just installed — not a store stub, not an old 2.7, not a conda env you do not remember creating.

Create a folder for practice. Something boring and local is fine: Documents/python-practice. Open that folder in VS Code (File → Open Folder). Do not paste files into a random Downloads pile.

Run your first .py file

Create hello.py in that folder:

from datetime import datetime

now = datetime.now().strftime("%H:%M")
print(f"Python is installed. Time on this machine: {now}")

This is not a toy slogan. It imports a standard-library module, formats a value, and prints one line. If this runs, your interpreter, editor, and terminal agree.

In VS Code, open hello.py, then:

• Click Run Python File, or
• Open the integrated terminal and run:

Windows:

python hello.py

Mac:

python3 hello.py

You should see one line with the current time. If the editor shows a play button that does nothing, you picked the wrong interpreter. Select it again.

PATH mistakes that eat the rest of the evening

These are the usual ones:

• Forgot "Add to PATH" on Windows. Re-run the installer, enable PATH, open a new terminal.
• Windows Store alias. Disable the app execution aliases for python, then retry python --version.
• Old terminal tab. PATH updates do not apply to windows that were already open. Close them.
• Two Pythons. where python (Windows) or which python3 (Mac) should point at the install you just made. If it points at something else, select that interpreter in VS Code explicitly, or fix PATH.
• pip talks to a different Python. Always python -m pip / python3 -m pip.

Do not "fix" this by installing Anaconda on top of a broken PATH. You will have three Pythons and no extra time.

What not to install tonight

Skip these unless a later lesson asks:

• Anaconda / Miniconda
• Docker
• Jupyter, unless you already use notebooks at work
• Extra VS Code themes and AI plugins
• A second editor "just in case"

Every extra installer is another way to miss the 30-minute window.

A 30-minute checklist

Minute 0–10: install Python, tick PATH (Windows), new terminal, --version works. Minute 10–20: VS Code + Python extension + interpreter selected + folder opened. Minute 20–25: hello.py runs. Minute 25–30: write down the exact commands that worked on your machine (python vs python3). Tomorrow-you will not remember.

If you run over, stop after hello.py. Do not start pip-installing libraries until the hello file is boringly reliable.

After the install: syntax, not more tools

An environment is not a course. You still need variables, control flow, functions, and a first program that uses a library. That is what short evening lessons are for.

If you want a path that assumes you already have a job and a calendar, start with Introduction to Python Programming. Nineteen published lessons, written to be done in modest after-work blocks. Check the course page for the current enrollment window. Do not wait for a three-day workshop you cannot attend.

Tonight you only needed this: Python 3, pip, VS Code, one .py file. That is enough to sit down tomorrow and write actual code.