Parents GuideScratchPython

How to Know Your Kid Is Ready for Python (Not About Age)

Michael Murr··8 min read

Last updated: June 2026

A kid is ready for Python the moment they show "the spark", real recall and real logic, not at a specific age or after a specific number of sessions. Parents ask me weekly whether 9 is too young, whether 30 sessions of Scratch is enough, whether the 20-hour mark is the magic line. None of those numbers mean anything. The signal I look for shows up in 15 seconds at the start of a session, and once you know what to watch for, you stop needing the calendar.

This guide walks through what the spark actually looks like and the four behaviours that come with it. It also covers the kids who taught me to trust it (including the 30-session game-dev student I almost moved too late), and the question parents should ask instead of "what age." If you have been waiting for a fixed threshold before letting your child try Python, this is the post that ends that wait.

Key Takeaways

  • There is no fixed number for Python readiness. Not 2 months, not 20 hours, not 30 sessions. Age and hours are weak predictors.
  • The real signal is "the spark", the moment a kid can recall and re-explain last session's logic in their own words without prompting.
  • Four behavioural signs almost always accompany the spark: unprompted recall, independent debugging, original project ideas, and Scratch-limit questions.
  • Pushing Python before the spark produces frustration; waiting for the spark produces fluency. The difference is measured in months, not weeks.
  • After 20 years and 200+ kids, I have not once regretted moving a student to Python after the spark, and I have regretted moving them before it more times than I want to admit.

Table of Contents

Why There Is No Magic Number

The single most common question I get from parents is some version of "when should my kid switch from Scratch to Python?" Followed by a number. Is 9 old enough. Is 20 hours enough. Are 30 sessions the threshold.

There is no number. I have moved kids to Python at 9 who flew. However, I have kept kids in Scratch until 12 because the foundation was not there yet. Hours logged tell you almost nothing. For example, a child can sit through 40 sessions of Scratch following tutorials and never internalise a single concept. Another child can do 8 focused sessions and own the logic so completely that Python feels like translating a language they already speak.

The numbers feel reassuring because they give parents something to track. But they measure the wrong thing. What you actually want to measure is whether your child has built a mental model of programming. In practice, mental models do not show up on an hour counter. They show up the moment a child opens their mouth and explains last week's code back to you.

That moment is what I call the spark.

What the Spark Actually Looks Like

The spark is a 15-second test. It happens at the start of a session, before any new material.

I walk in (or log in, since we are online 1-on-1) and I ask, "Hey, what did we do last time?" That is the entire test. The answer tells me everything.

A child without the spark says "I don't remember" or "we made a game" or "something with the cat." That is fine. It just means the concepts have not stuck yet. We rebuild from there.

A child with the spark answers something like: "We made the score go up when the ball hits the paddle, and we used an if-block so it only counted when it actually touched, not just when it was close." That sentence contains three things. It has recall (they remember what we built), logic (they can re-state the conditional in their own words), and ownership (they say "we made" and "we used", not "you made").

That is the spark. Once I hear it consistently, the conversation about Python changes from "if" to "when." Usually within two sessions.

Four Behaviours That Come With the Spark

The spark almost never travels alone. When a child reaches it, three or four other behaviours show up in the same window. If you see most of these at home, your kid is ready.

BehaviourWhat it sounds likeWhy it signals readiness
Unprompted recall"Last time we made the variable go up by 1 each round"They are storing concepts, not following steps
Independent debugging"Wait, my sprite is not moving, let me check the loop"They have a mental model to debug against
Original project ideas"Can we make a game where you collect coins?"They are using the tool, not just learning it
Scratch-limit questions"Can it save my high score?" "Can it run on its own?"They are bumping into the actual ceiling of Scratch

If your child does three out of four of these things in a typical month, the spark is there. If they do all four, you are past ready. If they do one or zero, Scratch is still doing useful work and Python will hurt more than help.

For the deeper version of this checklist with the wait signals, my when should kids switch from Scratch to Python guide breaks down the full diagnostic.

The 30-Session Game Dev Kid Who Loved Python More

The kid who finally convinced me to trust the spark over the number was a long-time game development student of mine. He had done close to 30 sessions of Unity by the time we talked about Python.

He had struggled with if-statements at the start. His mom had been worried. We went slow, rebuilt his confidence, layered in conditionals, then loops. By session 30 he was running. He loved Unity. He loved game dev. And honestly, that was the problem in my head. I had this kid who was finally clicking after a long climb. Still, I was about to put him in front of Python, a slower language with text instead of sprites and no character moving across the screen at the end of session one.

I was sure Python was going to kill it for him. I almost did not move him.

What changed my mind was the spark. He had it. He could re-explain Unity logic in his own words. He was asking questions about saving game state that Unity makes harder than it should be. He was ready, even if my gut said the timing was wrong.

We moved him to Python. He loved it more than game dev. Not "tolerated it." Loved it. The shift from sprites to text did not kill anything because the logic was what he had fallen in love with, not the visuals. The spark told the truth. My worry did not.

That is when I stopped trying to predict Python readiness from session counts. The 30-session number meant nothing. The spark meant everything.

What Parents Usually Ask Instead (and Why It Misleads)

When parents try to time the Scratch-to-Python transition without the spark framework, they usually fall back on one of these three questions. None of them work well.

"Is my kid old enough?" Age is a weak predictor. Stronger than nothing, weaker than recall. For example, I have moved confident 9-year-olds successfully and held back 11-year-olds who needed more Scratch. The age question gives parents a number to anchor on, but the number is borrowing reassurance from biology that it has not earned.

"How many hours of Scratch do they need?" I get the appeal of this one. Hours feel measurable. But hours measure exposure, not absorption. A kid following YouTube Scratch tutorials for 40 hours can still come out unable to build anything from their own head, which means they cannot debug, which means Python will be painful.

"What if they finish a certain course?" Completion does not equal mastery. I have met kids who completed structured Scratch courses and still could not answer "what did we do last time?" Course completion is a paperwork milestone, not a cognitive one.

What works instead is asking the question I ask at the start of every session. Try it yourself this week. The answer will tell you more than any course platform's progress bar ever will.

For more on why kids learning to code by following tutorials is not the same as kids actually learning to code, see our piece on Roblox and Minecraft modding vs real coding.

How to Test for the Spark at Home This Week

You do not need to be a programmer to run this test. You just need to be paying attention at the right moment.

Three things to try in the next seven days:

  1. The recall test. Right before your child's next coding session (or right after the last one), ask "what did you do last time in Scratch?" Listen to the answer. Was it concept-level ("we made the score count when the ball hit") or vague ("we made stuff")?
  2. The original-project test. Ask "what would you want to make if you could make anything in Scratch?" A kid with the spark has an answer ready, often a specific one. A kid without it usually says "I don't know" or names a game they have seen.
  3. The bump-into-the-ceiling test. Listen for the next time your child says something Scratch cannot do. "Can I save my score so it remembers next week?" "Can my game be a real app?" When that question shows up unprompted, the ceiling has been reached.

If you get one strong yes out of three, give it another month and re-test. If you get two, talk to a tutor. As a result, if you get three, your kid is past ready and Python is waiting.

According to python.org, Python is one of the friendliest first text-based languages because of its readable syntax. That readability only pays off if the underlying logic is already there, which is exactly what the spark confirms.

Frequently Asked Questions

Is there a minimum age for Python? There is no hard minimum. I have started motivated 9-year-olds in Python successfully when the spark was clearly there. Most kids land in the 10 to 12 range, but age is a tiebreaker, not a rule. The spark is the deciding factor.

My kid has done 30 sessions of Scratch. Are they ready for Python? Probably, but the session count is not why. Run the recall test. If your child can re-explain what they built last session in their own words, with the logic intact, they are ready regardless of how many sessions it took to get there. Some kids reach the spark in 8 sessions, others in 40.

What if my kid does not want to leave Scratch? Resistance is usually about losing the thing they love (sprites, animation, immediate visual feedback), not about Python itself. A good tutor bridges that by translating one of their Scratch projects into Python side by side in the first session, so Python feels like a new way to do what they already love, not a replacement.

Can my kid skip Scratch and go straight to Python? Sometimes, usually for kids 13 and older or for kids with strong logic foundations from chess, math competitions, or another language. However, for most 8-to-11-year-olds, skipping Scratch trades one month of saved time for six months of fighting syntax without a mental model. The math does not work.

How do I know if my kid is faking the spark? You can not really fake recall. The test catches faking automatically because the child has to explain how something worked, not just name it. "We made a game" is not the spark. "We made the cat say hi only when you clicked it, with an if-block" is the spark. If you are unsure, ask a follow-up question. The spark survives follow-ups; faking does not.

The Bottom Line

Python readiness is a cognitive moment, not a calendar moment. The kids who succeed in Python are the ones whose Scratch foundation is real enough to support a new notation, and you can spot that foundation with one 15-second question at the start of any session.

Want a tutor's read on whether your child is ready for Python? Book a free Discovery Call and we will run the spark test live, walk you through what your kid said, and tell you honestly whether Python is next or whether Scratch still has work to do.

Enjoyed this article?

Your child can learn this and more with a dedicated 1-on-1 tutor.

Book a Free Discovery Call