On May 4, 12:12 pm, Joshua Smith <[email protected]> wrote: > Fair enough. > > I'd recommend that you update the documentation of db.Model to point out that > "the Model class is not designed for multiple inheritance" > if it doesn't already say that somewhere I didn't see.
Will get this taken care of by our doc team. > My workaround right now is to have my Model create a helper object and use > manual delegation patterns to get the calls done. It's kind of gross. Is > there a pythony way that would allow my model to present itself as a tzinfo, > without using multiple inheritance? I don't mind having the delegate inside > my model, but I'd rather not have to have all my callers get the delegate > through an extra call (or, in principle, even know about the delegate). I'm not fully following your use case, but perhaps it could be done the other way around? I.e. create a subclass of tzinfo that has a reference to a Model instance? --Guido van Rossum -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
