#python#setupBeginner

Python Local Setup Checklist: Python, pip, venv, IDE

Jun 10, 2026
40 min read

AI Insights

Powered by GPT-4o-mini

Verified Context: python-local-setup-checklist-python-pip-venv-ide
Quick Answer

Use this complete Python setup checklist to verify Python, pip, uv, virtual environments, VS Code, Jupyter, Git, project folders, and troubleshooting basics.

Quick Summary

Follow this comprehensive Python setup checklist to ensure your environment is ready for development with Python, pip, venv, and more.

Complete Python Local Setup Checklist: Python, pip, uv, venv, VS Code, Jupyter, Git, and Projects

Quick Answer

Your Python setup is complete when Python, pip, virtual environments, uv, your IDE, Jupyter, Git, and a clean project folder all point to the same environment.

Last verified: June 9, 2026.

Official Links

1. Python Installed

Windows:

powershell
python --version
py --version
py -0p
pymanager help
pymanager list
where.exe python
where.exe py
where.exe pymanager

If py list works on your machine, Python Install Manager owns py. If py list fails with a legacy launcher warning, use py -0p and pymanager list instead.

macOS:

bash
python3 --version
which python3
echo $PATH

Expected:

text
Python 3.14.5 or another current Python 3 release

Acceptable fallback:

text
Python 3.13 if a package or course does not support 3.14 yet

2. pip Working

Windows:

powershell
py -m pip --version

macOS:

bash
python3 -m pip --version

Expected:

text
pip ... from ... Python ...

The exact version can change. The important part is that pip runs through the Python you expect.

3. Virtual Environment Working

Windows:

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

macOS:

bash
mkdir setup-check
cd setup-check
python3 -m venv .venv
source .venv/bin/activate
python -c "import sys; print(sys.executable)"

Expected path contains:

text
.venv

4. Package Install Working

Inside the activated environment:

bash
python -m pip install requests
python -c "import requests; print(requests.__version__)"

If this works, package installation is working.

5. requirements.txt Working

Create:

bash
python -m pip freeze > requirements.txt

Reinstall:

bash
python -m pip install -r requirements.txt

You should commit requirements.txt, not .venv.

6. uv Installed

Windows:

powershell
uv --version
where.exe uv

macOS:

bash
uv --version
which uv

If uv is missing, install from:

text
https://docs.astral.sh/uv/getting-started/installation/

Check Python management:

bash
uv python list
uv python install 3.14

7. IDE Ready

Choose one:

VS Code required extensions:

IDE checklist:

  • open the project folder, not only one file
  • select the .venv interpreter
  • run a .py file
  • verify sys.executable points to .venv

Test file:

python
import sys

print("IDE is working")
print(sys.executable)

8. Jupyter Ready

Inside .venv:

bash
python -m pip install jupyterlab ipykernel
jupyter lab

If jupyter lab fails:

bash
python -m jupyterlab

Inside a notebook:

python
import sys
print(sys.executable)

The path should contain .venv.

9. Git Ready

Install Git:

text
https://git-scm.com/downloads

Check:

bash
git --version

Configure once:

bash
git config --global user.name "Your Name"
git config --global user.email "you@example.com"

10. Project Folder Ready

Recommended structure:

text
my-python-project/
  README.md
  requirements.txt
  .gitignore
  src/
    main.py
  data/
  tests/
  .venv/

.gitignore:

gitignore
.venv/
__pycache__/
*.pyc
.env
.DS_Store
.ipynb_checkpoints/

11. First Test Script

Create src/main.py:

python
import sys

try:
    import requests
except ImportError:
    print("Requests is not installed")
else:
    print("Requests is installed")

print("Python executable:")
print(sys.executable)

Run:

bash
python src/main.py

Expected:

text
Requests is installed
Python executable:
... .venv ...

12. Windows Master Checklist

powershell
python --version
py --version
py -0p
pymanager help
pymanager list
where.exe python
where.exe py
where.exe pymanager
py -m pip --version
py -3.14 -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install requests
python -c "import sys; print(sys.executable)"
python -c "import requests; print(requests.__version__)"
uv --version
git --version

If PowerShell blocks activation:

powershell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

13. macOS Master Checklist

bash
python3 --version
python3 -m pip --version
which python3
echo $PATH
python3 -m venv .venv
source .venv/bin/activate
python -m pip install requests
python -c "import sys; print(sys.executable)"
python -c "import requests; print(requests.__version__)"
uv --version
which uv
git --version

If a newly installed command is missing:

bash
source ~/.zshrc

or restart Terminal.

14. Which Setup Should You Choose?

Learner goalRecommended setup
Absolute beginnerPython from python.org, venv, pip, VS Code
Data science learnerPython, venv, pip, JupyterLab, VS Code
AI project learnerPython, uv, VS Code, Jupyter when needed
Backend or CLI learnerPython, uv or venv, Git, VS Code or PyCharm
Company laptopUse company-approved Python and ask before changing PATH or proxy settings
Mac user with Homebrew already installedHomebrew Python or python.org Python, but keep one clear project environment

The best setup is not the one with the most tools. It is the one where terminal, IDE, and Jupyter all use the same project environment.

15. Copy-Paste Windows Setup Recipe

Use this after installing Python and VS Code.

Choose the first venv command based on the Python you want:

powershell
# Use the Python that `python` currently points to
python -m venv .venv

# Use Python 3.14 through legacy Python Launcher
py -3.14 -m venv .venv

# Use Python 3.14 through Python Install Manager
pymanager exec -V:3.14 -m venv .venv
powershell
mkdir my-python-project
cd my-python-project
py -3.14 -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install --upgrade pip
python -m pip install requests
mkdir src
Set-Content -Path src\main.py -Value 'import sys, requests; print("Python works"); print(sys.executable); print(requests.__version__)'
python src\main.py
python -m pip freeze > requirements.txt

Create .gitignore:

powershell
Set-Content -Path .gitignore -Value ".venv/`n__pycache__/`n*.pyc`n.env"

Expected result:

text
Python works
... .venv ...
requests version

16. Copy-Paste macOS Setup Recipe

Use this after installing Python and VS Code.

bash
mkdir my-python-project
cd my-python-project
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install requests
mkdir -p src
cat > src/main.py <<'PY'
import sys
import requests

print("Python works")
print(sys.executable)
print(requests.__version__)
PY
python src/main.py
python -m pip freeze > requirements.txt

Create .gitignore:

bash
cat > .gitignore <<'EOF'
.venv/
__pycache__/
*.pyc
.env
.DS_Store
EOF

Expected result:

text
Python works
... .venv ...
requests version

17. Network Or Company Laptop Checklist

If package installs fail on a school, office, or company laptop:

  • confirm whether the network blocks PyPI
  • ask for proxy settings if required
  • ask for the company certificate file if SSL verification fails
  • avoid sudo pip
  • avoid random --trusted-host commands
  • use .venv even when the machine has a managed Python

18. What To Learn Next

After setup, learn in this order:

  1. Python variables and data types
  2. conditionals and loops
  3. functions
  4. lists, dictionaries, tuples, and sets
  5. file handling
  6. error handling
  7. pandas and NumPy
  8. projects

FAQ

How do I know my setup is truly correct?

Run sys.executable from terminal, IDE, and notebook. They should point to the environment you expect.

Should I use Python 3.14 or 3.13?

Use Python 3.14.5 or the latest stable version unless your package, course, or company requires 3.13.

Should I use VS Code or PyCharm?

Use VS Code for a flexible editor. Use PyCharm for a Python-first IDE. Either is fine if the interpreter is correct.

What is the most important habit?

Use one virtual environment per project and install packages into that environment.

Final Green Checklist

Your setup is complete when:

  • Python command works
  • pip works through Python
  • .venv activates
  • package install works
  • requirements.txt can recreate packages
  • uv works
  • IDE uses .venv
  • Jupyter kernel uses .venv
  • Git works
  • project folder is clean
  • .venv and .env are ignored

Keep this checklist nearby whenever you start a new machine or a new project.

Frequently Asked Questions

How can I verify if Python is installed on Windows?
You can verify if Python is installed on Windows by using the command 'python --version' or 'py --version' in PowerShell.
What should you do if the 'py list' command fails with a legacy launcher warning?
If 'py list' fails with a legacy launcher warning, use 'py -0p' and 'pymanager list' instead.
How can you check if pip is working on macOS?
On macOS, you can check if pip is working by running 'python3 -m pip --version' in the terminal.
What is the expected output when verifying a virtual environment on macOS?
The expected output when verifying a virtual environment on macOS is that the path contains '.venv'.
Where can you find the installation instructions for 'uv' if it is missing?
If 'uv' is missing, you can find the installation instructions at 'https://docs.astral.sh/uv/getting-started/installation/'.

Related Work

See how this thinking shows up in shipped systems.

Udemy Enroller

FastAPI Browser-Workflow Automation

Background job processor utilizing headless browsers and message queues to automate enrollments.

PythonFastAPICeleryAutomation
Adticks

AI Visibility & SEO Auditing Platform

End-to-end platform for tracking visibility across traditional search engines and AI generative engines.

Next.jsFastAPIPlaywrightSEO
Technical Blog

RAG-Powered Learning Platform with AI Assistant

Custom blog platform featuring contextual vector search and an embedded AI copilot.

RAGVector SearchLLMsFastAPI