Programming & Web Development · Guide
How to learn Python from scratch
The order that works, what to skip at the start, and the habit that separates people who learn Python from people who keep restarting chapter one.
The Nextversity teamProgramming & Web Development schoolUpdated August 10, 20266 min read

On this page
- The short answer
- Stage 0: setup (30 minutes, once)
- Stage 1: the six building blocks (10 to 15 hours)
- Stage 2: making programs survive reality (8 to 12 hours)
- Stage 3: pick one direction (20+ hours)
- The habit that decides whether this works
- What to skip early
- Resources worth the time
- When not to enroll
- Where to learn it
The short answer
Learn Python in this order: setup, then the six core building blocks, then functions, then files and errors, then one library, then a real project. Give it 30 to 60 minutes most days and you will be writing useful scripts within a few weeks.
The order matters more than the resource. Almost everyone who stalls did the same thing: jumped to a framework or a data library before conditions and loops were automatic, then found that nothing made sense.
Stage 0: setup (30 minutes, once)
Install the current Python 3 from python.org and an editor. VS Code is the common choice and is free.
On Windows, tick "Add Python to PATH" in the installer. That single checkbox is responsible for a large share of first-day frustration. On macOS and Linux, use python3 in the terminal rather than python.
Then get print("hello") running from a saved file, not just the interactive prompt. That is the setup done.
Stage 1: the six building blocks (10 to 15 hours)
Everything else is made of these:
- Variables and types. Strings, integers, floats, booleans. What each can do.
- Conditions.
if,elif,else, and comparison operators. - Loops.
forover a list,whileuntil something changes. - Lists. Ordered collections, indexing, slicing, appending.
- Dictionaries. Key-value pairs. Underused by beginners, used constantly by everyone else.
- Functions.
def, parameters,return. There is a full guide to writing functions when you get here.
Do not move on until you can write these without looking them up. Not memorized: fluent. That distinction is the whole game.
Stage 2: making programs survive reality (8 to 12 hours)
- Reading and writing files, including CSV.
- Errors and exceptions, with
tryandexcept, so a program does not stop dead at the first surprise. - Modules and imports, including the standard library, which is huge and free.
- Virtual environments and pip, so installing packages does not eventually break your machine.
This stage is unglamorous and it is where scripts become tools other people can run.
Stage 3: pick one direction (20+ hours)
Now specialize, because "learn Python" stops being a useful goal here:
- Automation:
os,pathlib,shutil,requests, plus openpyxl for spreadsheets. - Data: pandas, then plotting. Pairs naturally with SQL.
- Web: Flask or Django, on top of HTML and CSS.
- Everything else: object-oriented programming, testing, and structuring a project properly, which the advanced Python certificate covers.
Pick one. Two at once halves the speed of both.
The habit that decides whether this works
Build small things, constantly, from week one.
Not tutorial projects. Things you want: a script that renames your photos by date, one that pulls the numbers out of the monthly report, one that checks a page for a price change. They will be ugly. They will work, and that changes how you feel about the whole endeavor.
Watching tutorials feels like progress. So does reorganizing your desk. Only one of them ends with a program that runs.
The tutorial trap is real: you can follow along with forty videos, understand every line as it is typed, and freeze at an empty file. The cure is to close the video and write something without it, immediately, even badly.
What to skip early
- Object-oriented programming. Important later, confusing at week two.
- Type hints. Useful in real projects, noise while learning.
- Frameworks. Django before functions is a reliable way to feel stupid for no reason.
- The perfect setup. Your editor configuration is not why you are stuck.
Resources worth the time
The official Python tutorial is free, thorough and accurate. PEP 8 is the style guide everyone follows, worth skimming once you can write code that runs.
A structured course is worth it when free resources have not stuck, because the value is the order and the deadline, not secret information.
When not to enroll
If you have a Python course open that you stopped in week two, restart that one rather than buying another. The five-course graveyard is a real pattern and a sixth purchase does not fix it.
If you need one script written once, an AI assistant or a search may get you there today. Learn the language when you want the capability.
Where to learn it
The Python certificate covers stages 1 and 2 with practice throughout, and the advanced certificate covers structure and real projects. One subscription opens both plus the whole Programming & Web Development school.
Thirty minutes a day and one small script a week. That is the entire method.
Questions people ask
Can I learn Python on my own?
Yes, and most people do. The obstacle is not information, it is structure and follow-through. Pick one path, build small things constantly, and avoid switching resources every time you get stuck.
What should I learn first in Python?
Variables, data types, conditions, loops, lists and dictionaries, then functions. Those six carry you through almost everything else, and skipping ahead is the most common reason people stall.
Do I need to be good at maths to learn Python?
No. Everyday programming needs arithmetic and logic, not advanced maths. Specific fields like machine learning or graphics do need more, and you can add it when you get there.
Which Python version should I learn?
The current Python 3 release from python.org. Python 2 reached end of life years ago, so ignore any tutorial still using it, which you can spot by print statements written without brackets.
How long before I can build something useful?
A genuinely useful script, one that renames files or reformats a spreadsheet, is achievable within a few weeks of regular practice. Larger applications take months.