Skip to main content

0.2 Environment Setup

Minimal AI course setup kit

Install less first. The goal is only: enter one folder, run Python, save code with Git, and keep enough evidence that another person can rerun your work.

Install Now

ToolUse
BrowserCourse, Colab, GitHub, AI tools
VS CodeEdit files
Python 3.11Run examples
GitSave checkpoints

Install Docker, CUDA, vector databases, and large frameworks later. Installing too much too early makes beginner errors harder to locate.

Choose One Python Command

Different machines use different Python launchers. Pick the first command that works and keep using it in your notes.

SystemTry firstIf that fails
macOS / Linuxpython3 --versionpython --version
Windows PowerShellpy -3.11 --versionpython --version
Colabno install neededuse the notebook runtime

When a later command says python, replace it with the command that worked on your machine.

Five-Minute Check

python3 --version
git --version
mkdir ai-learning-lab
cd ai-learning-lab
python3 -m venv .venv
source .venv/bin/activate
python -c "print('AI course environment is ready')"
git init

Windows PowerShell activation:

py -3.11 -m venv .venv
.\.venv\Scripts\Activate.ps1

Expected signal:

AI course environment is ready
Initialized empty Git repository ...

If The Check Fails

SymptomDo this firstKeep as evidence
python3 not foundTry the command table above, then install Python 3.11The command and full error
virtual environment activation failsCheck your shell: zsh/bash uses source, PowerShell uses Activate.ps1Shell name and activation command
git not foundInstall Git, reopen the terminal, retry git --versionVersion output or error
permission errorMove the project under your user folder, not a protected system folderCurrent directory from pwd

If this still fails, use Colab for now and return after Chapter 1. The pass line is simple: enter a folder, run Python, initialize Git.

What Experienced Learners Should Check

If you already have a setup, do not skip the page completely. Confirm that you can explain:

  • Which interpreter runs this course project.
  • Where dependencies will be installed.
  • How you will recreate the environment on another machine.
  • Which files should be committed and which should stay local.

The environment is part of the course output. A project that only works on your laptop is not finished yet.