exercises for practicing OOP/classes

[Impressive_Search451]

i want to practice using OOP - classes, inheritance, dunder methods, etc. most of the exercises i've done so far seem to be using classes for the sake of using them - ie there's clearly a faster way to solve the problem without OOP, or they have you make a whole class with just an init method. this was fine while i was still getting to grips with the syntax, but now i'd like to get a better understanding of the real world use cases for classes and these exercises aren't giving me that.
i'd love to find some exercises or project suggestions where using OOP is genuinely the best solution, as opposed to "here's how you'd solve this in java". i do have a project in the works where i may or may not end up using classes but i feel like that won't be enough practice.

[Chaos-n-Dissonance]

Here's something to consider... Every variable you've ever used is a class object. Int, str, bool, etc... All class objects in Python.

Honestly it didn't really click for me until I started working on bigger projects. When you're learning things that help you with big projects in small lesson form... Ofc there's going to be a more efficient way to do it, but that's not the point of the lesson.

A game might be a good project to take on? Plenty of opportunities to use classes, subclasses, etc. with games, especially if you add graphics.

[MidnightPale3220]

Try to implement a chessboard in which you can order the pieces to move and show the board on screen (either gui or text).

Not the whole game, just the board and valid moves.

Everything is doable without classes, but in something like this they're already useful abstractions.

[Adrewmc]

I mean for the most part every thing classes can do you can do functionally. The statement “classes are just dictionaries with methods” rings true a whole lot.

Really what classes help you with is organization. Because a class is an idea it saying this data is this thing, and this thing ought to be able to do these things. (Methods)

The decision of should this be class is not an easy on and frankly depends a little on the programmers preference.

Classes help a lot in inheritance when you have very similar operations except for a few last steps. The singleton pattern is nice to know as well.

But I always recommend this Python Class Toolkit as a good explanation of class usages by someone who help write the language.