Python path: 59 days from zero to your first scripts
Fifty-nine one-hour sessions, one a day, in four modules, for people who have never written a line of code. The goal: go from "I know nothing about this" to "I built a tool I use every day". No prerequisites, no jargon left unexplained, only one new idea per session at the start.
Why Python, and for whom
Python is the language most often recommended to beginners: its syntax reads almost like English, it installs for free on Windows, macOS and Linux, and it is used everywhere — automating tasks, processing files, analysing data, making web services talk to each other. This path is the front door of this site for the least technical readers: every term is defined the first time it appears, every exercise uses free tools, and every session ends with a small visible success.
The method, the same every day
| Time | Phase | What you do |
|---|---|---|
| 20 min | Theory | The session's lesson (on the module page), read calmly, taking notes. |
| 30 min | Practice | You type code yourself, you run it, and you SEE it work. Every exercise has an explicit success criterion. |
| 10 min | Recap | Three lines in the notebook, then redo today's exercise without notes. |
Typing the code by hand matters as much as understanding it: never copy-paste an example, retype it. The typos you fix are exactly the errors you will know how to repair later.
The tools, installed once (day 1)
- Python 3.12 or newer, from python.org/downloads — free, official, for every system. On Windows, tick the "Add python.exe to PATH" box during installation: it makes the
pythoncommand available everywhere. - A text editor: VSCodium (the fully open-source build of Visual Studio Code) is recommended, but Windows Notepad or TextEdit on a Mac are enough to start. A code editor is not a word processor: it saves plain text, with no formatting.
- The terminal: the window where you talk to the machine by typing text. "Terminal" or "Command Prompt" on Windows, "Terminal" on macOS and Linux. The whole path happens there: you write in the editor, you run in the terminal.
- A digital notebook: a plain folder of text files, one file per day.
No account to create, no bank card, no subscription: the whole path fits in these three free tools.
The golden rule
One hour every day beats seven hours on Sunday. If you miss a day, do not catch up the next day: shift everything by one day, and trim module 4. Sessions are numbered D1 to D59 with no calendar dates: only order and regularity matter.
Learning with an AI, without letting it code for you
This path can be followed with an AI as a tutor, ideally a model running at home (see your first local model): your experiments never leave your machine. It saves you time when it makes you work, and wastes it when it works in your place.
- Ask it to explain an error, to quiz you, to proofread your code. Not to write the exercise: the day you want to automate something on your own, it will not be inside your head.
- Never copy its code without rereading it line by line and running it yourself. A model writes plausible code that sometimes does not run.
- Check what it claims against the official documentation, docs.python.org: a model can be confidently wrong, even about simple code.
- Never paste passwords, personal data or private file contents into it.
Every session ends with an "Agent tips" box: how an agent (Claude Code, Kimi Code, OpenFox) would do the same task, the trap to avoid, and the proof to demand. You learn by hand, and along the way you learn to delegate without being fooled.
The four modules
Each module is one page: the sessions follow one another, each with its goal, its lesson, its step-by-step practice and its recap. Tick a module when all its sessions are done; your progress stays in your browser.
Recommended free resources
- The official Python tutorial — the reference to keep at hand for the whole path.
- Automate the Boring Stuff with Python (Al Sweigart, free online) — the book that inspires module 4: automating real tasks.
- The Python standard library — the list of everything Python can do without installing anything (modules 3 and 4).
- The Python wiki's Beginners Guide — pointers for every next step after the path.
The end-of-path checklist
- I write a small Python program and run it in the terminal without help.
- I handle variables, numbers, text, lists and dictionaries.
- I read and write files, including a CSV.
- I read a Python error message (traceback) and find the faulty line.
- I write a function and test it with pytest.
- I install a library in a virtual environment and use it.
- I have automated a real task from my daily life (rename, sort, count).
- I have a finished, documented project whose every line I can explain.
A box left unticked is not a failure: it is the list of what you will pick up first.
- 1Python module 1: install, write, reactDays 1 to 14: install Python, the terminal, print, variables, numbers, text, input, if/else — one small win a day, no jargon.
- 2Python module 2: loops, lists, dictionaries, filesDays 15 to 28: while and for, lists, dicts, tuples, sets, reading and writing files, catching errors, and parsing a CSV by hand.
- 3Python module 3: functions, modules, libraries, debuggingDays 29 to 42: writing functions, importing modules, venv and pip, requests and pathlib, reading a traceback without fear, and automating file tasks.
- 4Python module 4: a real project, tested and finishedDays 43 to 59: structuring a project, argparse, logging, pytest, the csv module, and the final project: a command-line expense summariser, documented.