>If I didn't think combining the functionality in models would confuse >people (particularly newcomers), I could probably agree with you. But >regardless, I think it's cleaner to keep these functionalities >physically separate.
And you honestly think that newcomers are not confused by the fact that they have to use a get_list method on a module they themselves wrote, but didn't include that method? It _is_ magically-instantiation-of-methods still, that's what upsets Robert. If I write a module, I (as in "I == newcomer") don't expect function to magically come into existence. If I write a class that inherits from meta.Model, I am completely fine with classmethods I inherit from that class I am inheriting from. So the _cleaner_ approach to store class-level stuff would be in class methods, as those are the things people would expect if they know zilch about Django but do know about Python. I could live with both solutions - heck, I can even live with the current situation - but the classmethod approach _is_ the cleaner one. At least if we still talk about Python ;-) bye, Georg
