Moving Beginners From Scratch to Python Without the Crash
A child who built a whole maze game in Scratch sits down in front of Python, types one line, gets a red error about a missing bracket and decides they are "not good at real coding." The move from Scratch to Python is where many young...

A child who built a whole maze game in Scratch sits down in front of Python, types one line, gets a red error about a missing bracket and decides they are "not good at real coding." The move from Scratch to Python is where many young coders quietly give up, and it is almost never because the ideas are too hard.
I have run this transition with about a dozen groups of 10 to 14 year olds at our club. The concepts carry over well. What breaks is the feeling of control. In Scratch, nothing can be misspelled. In Python, everything can. This guide is the plan I now use, session by session, with the reasons behind it.
When a learner is ready to go from Scratch to Python
Age matters less than people think. I look for three signs instead:
- They use variables on purpose, for a score or a timer, not by accident.
- They have used a "repeat until" or "if then else" block to solve a problem they set themselves.
- They get annoyed at Scratch, for example because a project with 40 sprites has become hard to manage.
That third sign is the best one. Frustration with the tool means they are reaching past it. A learner who still enjoys dragging blocks and has not hit any limits can stay in Scratch longer with no harm done.
Typing speed matters too. If a child types fewer than about 15 words a minute, Python becomes a typing lesson. Ten minutes of typing practice at the start of each session for two weeks fixes most of that.
Map the blocks they already know
Before writing any Python, I put a Scratch project on the screen next to a blank Python file and translate it together. The point is to show that nothing new is being learned yet, only a new way of writing it down.
| Scratch block | Python version | What trips beginners up |
|---|---|---|
| say "Hello" | print("Hello") | Forgetting the quotes or the closing bracket |
| set score to 0 | score = 0 | Thinking = means "is equal to" |
| change score by 1 | score = score + 1 | The line looks impossible as maths |
| repeat 10 | for i in range(10): | The colon and the indented block |
| if then else | if, else, with a colon each | Using = instead of == |
| ask and wait | input("Your name? ") | Input always returns text, not a number |
Print this table and stick it on the wall. Learners will look at it for weeks, and that is fine. If the variable idea needs more groundwork, our guide on explaining variables to beginners without the box metaphor pairs well with the second and third rows.
A four session plan that works
Each session is 60 to 75 minutes. Keep every program short enough to fit on one screen.
Session 1: print and input
Write a program that asks for a name and a favourite food and prints a silly sentence with both. Spend most of the time on errors. Make a typo on purpose and read the error message out loud together.
Session 2: variables and maths
Build a pocket money calculator: how many weeks to save 30 pounds at 2.50 a week? This introduces numbers, the int() conversion for input, and the "score = score + 1" pattern.
Session 3: if and else
Make a guessing game with one guess. The computer picks a number from 1 to 10 and says "too high", "too low" or "correct." Everyone finishes something playable in under an hour.
Session 4: loops
Turn the guessing game into a loop with five guesses and a counter. Now it feels like a real game, and it is the same game they could have built in Scratch, which is exactly the point.
After these four sessions, most of our learners are ready for small exercises such as our Python if else practice problems.
Do not rebuild their favourite Scratch game
The usual advice is to have learners recreate a Scratch project they love in Python, because it is motivating. I tried this for two terms and stopped.
The problem is graphics. Their Scratch platformer had sprites, sound and movement in an afternoon. The Python version, even with a library like pygame, needs a game loop, coordinates, event handling and image loading before a single character moves. After three sessions they have a rectangle sliding across a black window and feel they have gone backwards.
Text games protect motivation much better. A choose your own path story, a quiz, a number guessing game or a simple shop with prices and a wallet all feel finished within one or two sessions. Graphics can come later, once typing and indentation feel normal, usually after 8 to 10 weeks.
Handling the first wave of errors
The single biggest change from Scratch to Python is that errors exist. Scratch blocks cannot be put together wrongly in most cases. Python will refuse to run because of one missing colon.
Three habits help:
- Name the common errors. SyntaxError, IndentationError and NameError cover about 80 percent of what beginners see in the first month. Write them on the board with one cause each.
- Read the last line first. Teach learners to look at the bottom of the error message, then the line number.
- Do not grab the keyboard. Ask "what line does it point to?" and "what is different from the table on the wall?" Our article on helping a beginner debug without fixing the bug for them has more prompts like these.
I also tell every group that professional programmers see errors all day. A red message is information, not a grade.
Keep the setup simple, too. A browser based editor or a beginner editor with a large Run button removes installation problems from the first weeks. Saving files, folders and terminals can wait until learners have written ten or so small programs and want to keep them.
Frequently asked questions
What age should kids move from Scratch to Python?
Most learners are ready somewhere between 10 and 13, but readiness matters more than age. Look for confident use of variables, loops and if blocks, plus a typing speed of at least 15 words a minute. Some keen 9 year olds manage well, and some 14 year olds benefit from more time in Scratch.
Is Python harder than Scratch?
The ideas are the same, but Python is less forgiving. Spelling, brackets, colons and indentation all have to be exact. With a clear block to Python translation and short text projects, most beginners adjust within three or four sessions.
What should a beginner build first in Python after Scratch?
A short text game works best, such as a number guessing game or a quiz. These can be finished in one session and use the same ideas learners already know from Scratch. Leave graphics until typing and indentation feel comfortable.
More in Teaching Code
Teaching Code
How to Teach Beginners to Read Python Documentation
I ran a small test at club last February because I was tired of a specific pattern.
Teaching Code
How to Teach the Difference Between print and return
In week five of our adult evening group, a learner called me over because her code had stopped working.
Teaching Code
How to Train Volunteer Mentors for a Coding Club
Our club recruited nine volunteers in one term. Three were still turning up by week six.