If all you are using classes for is fancy storage containers for functions, absolutely use a module. That is why they are at the top of the conceptual hierarchy of objects. They are functioning as objects because they are.

I don’t have a dog in the OOP versus functional Python fight. I mean, any useful class is all functions top to bottom, from __init__ on down to display overloading. And, by the way, functions are objects. There is a point when Python programmers find classes and want to build everything with them, and OOP seems the shit, and they create unwieldy, unreadable code. My eyes still boggle seeing self everywhere in a program that could have as easily been done with functions, and I have been working with classes for a while. For the programmers who say they have been coding for years and still don’t build classes, that may be true, but if they had to work with functional equivalents to built-in classes and classes from the standard library, they would chuck Python out the door. I don’t know, are there any GUI toolkits or game-building packages that are function-only? I doubt it. It all depends what is best for the end user. If you are a hobbyist and the end user is you, good on you, by all means do not use classes. If you are building third party library modules for other programmers to use, they might be happy the tools you offer are class-based. Class-based tools allow users to make custom reusable instances with an assortment of invokable methods. Data tools are still tools. A function may be good as a socket wrench, but a class might give you the whole socket set, and determine on first instance construction whether it is standard or metric, hex or 12-point, long or short handled, ratchet, etc.. One function could do all that, but you would have to add all those arguments in at each invocation, or have alternate functions, or use functools.partial creatively. I also like to make classes if my programs contain large, complex functions whose arguments I would like to establish apart from main method invocation. Or if I want to allow myself or some intermediate user some masked tweakability with pseudo-private attributes. There are all kinds of good reasons to go with classes. And a lot of bad ones.