How to Install Python: A Safe Setup Guide

Before you install: decide what you actually need

For learning, web projects, automation, and most new applications, choose the latest stable Python release that your project’s dependencies support. Do not install a preview release just because it is newer. If you are joining an existing project, read its pyproject.toml, requirements file, README, CI configuration, or team instructions first: the project may require a specific Python minor version.

Install Python from a trusted source

Use the operating-system tab that matches your computer. The goal is not only to finish an installer: it is to know exactly which command launches Python, where it lives, and which pip belongs to it.

py list
py --version
py -m pip --version
py -c "import sys; print(sys.executable)"

Prove which Python will run your code

A version number alone is not enough. Machines often have several Python installations, and a bare pip command can point to a different one. Verify the interpreter executable and ask that same interpreter to run pip. These four facts must agree: the command you type, the version, the executable path, and the package installer.

py -c "import sys; print(sys.version); print(sys.executable)"
py -m pip --version

Create an isolated project environment

A virtual environment is a directory containing a project-specific interpreter and package location. It prevents one project’s dependencies from silently changing another project or your operating system. Put it inside the project as .venv so editors can discover it and so it is easy to delete and recreate.

mkdir hello-python
cd hello-python
py -m venv .venv
.\.venv\Scripts\Activate.ps1
python -c "import sys; print(sys.executable)"

1. 01

   Create the project directory

   Keep project source, its dependency files, and .venv together. Do not create a virtual environment in a random global folder and reuse it for unrelated applications.

2. 02

   Create .venv with the interpreter you verified

   Use py -m venv .venv on Windows or python3 -m venv .venv on macOS/Linux. The base interpreter chosen here determines the environment version.

3. 03

   Activate it only for convenience

   Activation changes your current shell so python and pip resolve to .venv. It is not required: .venv/Scripts/python or .venv/bin/python can be called directly in scripts and CI.

4. 04

   Check sys.executable after activation

   It should point inside the project’s .venv directory. If it does not, stop before installing packages; you are using the wrong interpreter.

import sys

print("Python is ready.")
print(f"Running: {sys.executable}")

python hello.py
python -m pip install --upgrade pip
python -m pip install requests
python -m pip show requests

Install packages without losing the interpreter

The safest package command is always interpreter -m pip. It asks the exact interpreter that will run your code to install or inspect its packages. This avoids the most common beginner failure: python runs one installation while pip writes to another.

python -m pip --version
python -m pip install requests
python -m pip show requests
python -c 'import requests; print(requests.__version__)'

• Use py -m pip in a Windows shell before .venv is active; after activation, python -m pip is usually clearest.
• Use python3 -m pip before activation on macOS/Linux; after activation, python -m pip refers to .venv.
• Do not use sudo pip or sudo python -m pip for project dependencies.
• Do not install every package globally 'for later'. Add a dependency only inside the project that uses it.
• If a project supplies requirements.txt or pyproject.toml, follow that project’s install command rather than inventing a different dependency format.

Troubleshoot the failure, not the symptom

Reset a broken project environment safely

A virtual environment is disposable. If it points to the wrong Python, has inconsistent packages, or cannot be repaired quickly, remove only that project’s .venv directory, recreate it with the intended interpreter, and reinstall from the project’s tracked dependency file. Never delete a system Python directory to fix a project environment.

# Deactivate first if the environment is active
deactivate
# Remove only this project's .venv directory using your file manager or shell
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements.txt

Finish with a setup you can trust

Next, learn the language before adding frameworks. Start with values, types, control flow, functions, files, and exceptions. Once that foundation is comfortable, build a small project and add dependencies one at a time with the environment already working.