hugo wrote: >>I'm sure others can come up with other methods. I would prefer 1) >>because its obvious, but don't really care as long as we get rid of the >>generated class. > > > Actually turning the model class with it's magic into one > standard-behaving python class (preferably new-style) would be a really > great thing. Because it would allow using that class in standard > situations like inheritance or multiple inheritance - I did work on > using MI for mixins (a rather common way to do it in Python), but had > absolutely no luck because of all that is going on in the machinery. > > So if we could come up with a way that turns the model class into > something that can be used in all situations where Python classes are > used, that would really be great and would even get a +2 from me ;-) > > (the place where I looked for Mixins was when trying to come up with > easier ways to do my AbstractSearching and AbstractTagging stuff) > > bye, Georg > >
I can't work out what you want here: 1) For the model class defined by the user to 'just work' for everything 2) For some generated class to 'just work' for everything I'm having a hard time seeing any benefit to 2 over 1, unless 1 can't be done. I think you want 1 (as do I), but I just couldn't quite see if that was what you meant in the text ;-)
