How long does it take to learn Python?
The shared core is about 30 hours across 17 skills. After that the answer splits by destination — scripting stops there, data work adds SQL and a library, web work adds a framework and HTTP. Most published figures quietly answer only the first.
It takes the same 17 skills and lays them out against the hours you actually have, with the checkpoints dated.
Price it against your week"Learn Python" is three different courses
This is why the estimates you find disagree by a factor of ten, and it is not because anyone is lying. Python is a language three largely separate populations use for three largely separate purposes, and the word covers all of them.
Somebody automating a spreadsheet task, somebody building an API and somebody cleaning a dataset need the same first fifteen hours and then diverge completely. An estimate is only meaningful once it says which of the three it is answering — so this page prices the shared core, which is the part every route needs, and then says what each destination adds. The official tutorial covers most of that core and is a fair thing to time yourself against.1
- Scripting and automation — the core, plus files and paths. The shortest honest route, and a real skill on its own.
- Data work — the core, plus SQL and one library. SQL is the bigger half and it is independent, so you can do it in parallel.
- Web and services — the core, plus a framework, HTTP and deployment. The longest, and the one where the core is most often skipped.
Where the published numbers go wrong
Two failures, and they push in the same direction.
The first is counting exposure. Hours of video watched are not hours of Python learned, and the gap is not a rounding error — material studied passively decays fast, with most of the loss inside the first day.2 A number built on watch time is measuring something that partly evaporates before the next session — which is the same reason the passive study strategies come out worst when techniques are ranked by evidence.3
The second is stopping at syntax. A course that ends when you can write a loop has priced the cheap half and called it the subject. That is how "learn Python in 30 days" survives contact with reality: it is true, for a definition of Python that stops before anything goes wrong.
If the destination is data, do SQL alongside
Worth saying plainly because it changes the plan rather than the estimate. SQL is 47 hours across 26 skills — larger than the Python core — it is what most analysis roles actually test, and it does not depend on Python at all. Two subjects at once halves your spacing on both, so the honest advice is sequential rather than simultaneous: core Python first because it is shorter, then SQL, then the library.
Sources, and what each is worth
Questions that come with this one
Can I learn Python in a month?
The core, yes, at about ten hours a week — 30 hours is roughly three to four weeks at that pace. What you will not have is a destination on top of it, and the destination is usually the reason you started.
Is Python harder than SQL?
Broader rather than harder. Python's core is 30 hours against SQL's 47, but Python keeps going afterwards and SQL mostly does not. SQL is deeper in a smaller space.
Do I need to learn Python before pandas?
Enough of it, yes. People who skip to pandas can usually follow a tutorial and cannot debug one, because the error messages are about Python and not about pandas. The core is the part that makes the errors readable.
How long before I can get a job with it?
Longer than the language takes, and the gap is not more Python. It is having work somebody else can inspect — which is why this site prices courses in hours and then asks you to hand something in.
Put this into practice
Reading about how to learn is the easy half. Tell us what you are actually trying to get good at, and we will build the path — the skills in the order they depend on each other, and marked work to prove you got there.
Build my path