Are there practical reasons for designing a method-only class/object?
Are there practical reasons for designing/implementing a method(s)-only class/object?
Follow-up background notes:
This question is for languages that are not exclusively Object-Oriented, for example, Python and Perl. So languages that can have classes/instances and top-level independent functions.
The event that started me thinking about this is that was reading some code that is a mixture of classes/object and independent functions. I wonder what things to evaluate when thinking about whether/is some of the independent functions should be grouped to classes/object.