There are millions of ways to make games, thousands of tutorials on the subject, and hundreds of tools you can use to do it.
If you want to learn how to make a character jump around in Unity - there’s other resources for that.
If you want to learn how to code a UI system from scratch in Rust - there’s bound to be resources for that too.
The reason I want to write this series is that, inevitably, the thing you want to make is going to be different from all the tutorials you can find. You’ll learn bits and pieces from different places - but if it’s not obvious how to put them all together, you’re going to feel frustrated. Like if there was just one tutorial that covered exactly what you needed - you’d be fine. But instead, you’re sticky-taping together code and it’s not working and you have no idea why or how to fix it.
This series isn’t really about learning how to make a game, or how to code in Python, (but it will involve both). I’m not going to cover setting up your environment, or the basics of coding (but you might pick up some of that stuff). The point of this series is to show how to structure and iterate on game code, so that you can more easily integrate things you learn in other tutorials, and fix the problems that might pop up while you’re doing it.
To follow this, you’ll need to have Python installed (version 3.7 or higher). You’ll also need to have Pygame installed. (It may not be the most advanced game engine in the world, but it’s fairly easy to use.) Lastly, you’ll need to know how to run a Python file - either from command line, or an editor like Visual Studio Code, or even just by double clicking it (if that happens to work on your machine).
As long as you’ve got that, you should be able to follow along with these tutorials. The repo with all the code for them is here: https://github.com/mistodon/pygame_tutorial - and if you just want to directly download that code so you can test it out before trying your own hand at it, you can do that here: https://github.com/mistodon/pygame_tutorial/archive/refs/heads/main.zip
You can then read Part 1 which will give you the broad strokes of how I would structure a game, and more importantly, why it helps you to do it that way.
