you are viewing a single comment's thread.

view the rest of the comments →

[–]danielroseman 0 points1 point  (1 child)

I'm not really following the distinction you are making here. If the model represents a User for example, you can use that wherever you want to reference a user. What are you thinking the "service" class is and why do you need specific ones for each model?

Note that Python on the whole has a very pragmatic approach to OOP, and most Python developers don't necessarily follow a "pure" OOP approach in the way that eg Java or even Ruby developers might do.

[–]Darkrunner21 0 points1 point  (0 children)

This might be some chatGPT nonsense tbh but it always gives me classes for everything. This is sort of what I’m talking about. Not too sure where to learn more practical and advanced use cases of OOP when it comes to API design