Set Up Your Workshop Environment
Get Python, a virtual environment, and the 14-demo pack ready before Day 1. Every demo also runs fully offline, so venue wifi is never a blocker.
Get your machine ready
in about 15 minutes.
Everything for the hands-on demos — Python, a virtual environment, and the 14-demo pack. Seven short steps, and every demo also runs offline, so venue wifi can't block you.
Hover a line to learn more
Six steps. About fifteen minutes.
The whole toolchain fits in one virtual environment. Below is each step, why it matters, and how to check it worked before Day 1.
Python 3.10 or newer
Everything runs on Python. Install it from python.org — not the Microsoft Store — and on Windows tick "Add python.exe to PATH" on the first screen. On Windows use the py launcher; python3 there opens the Store instead of running.
The workshop demo pack
Download the shared Google Drive folder and unzip it somewhere easy to reach. It holds 14 self-contained demos (00 to 13), a combined requirements-all.txt, and per-demo notes. Open a terminal inside that folder — every command below runs from there.
Virtual environment
Keeps the workshop packages separate from your system Python. Create it once, then activate it in every new terminal. On Windows PowerShell try Activate.ps1 first; if that does not work, use the lower-case activate.ps1. If PowerShell blocks the script, run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once.
Install dependencies
One command pulls every package the 14 demos use — anthropic, openai, mcp, flask, fastapi, scikit-learn, tiktoken and more. Each demo folder also has its own requirements.txt if you would rather install per demo.
API key · optional
Every demo runs offline in MOCK_MODE with no key. Add one only to see real model responses in demos 05 to 13. Copy .env.example to .env inside that demo folder and fill in ONE provider — Anthropic (ANTHROPIC_API_KEY) or OpenRouter (OPENROUTER_API_KEY). Never commit a real .env.
Run a demo to verify
Pick a demo that needs no key, install its requirements, and run the script named in its README. Output in the terminal means your environment is ready for Day 1. Re-run each demo you plan to follow along with at least once beforehand.
All commands, ready to paste.
Run these in order in your terminal. Each line is individually copyable. Use the Windows or the macOS / Linux line for your machine.
Check Python — Windows
Check Python — macOS / Linux
Enter the demo pack
Create virtual env — Windows
Create virtual env — macOS / Linux
Activate — Windows PowerShell
Activate — Windows PowerShell (lower-case — use if Activate.ps1 fails)
Activate — Windows CMD
Activate — macOS / Linux
Install all dependencies
Copy the env template — Windows
Copy the env template — macOS / Linux
Verify — run a demo that needs no key
Need help? Bring your laptop to the venue at least 20 minutes early. The team will help with any setup issues before the first session. If the network is flaky, every demo still runs in MOCK_MODE with no API key.