On May 4, 12:12 pm, Joshua Smith joshuaesm...@charter.net 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
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
Wow. You ask for help from a python guru, and you get it from THE
python guru.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email
On May 4, 11:17 am, Joshua Smith joshuaesm...@charter.net wrote:
I've worked around the problem by moving the tzinfo behavior into a helper
object and delegating all the calls, but it's not as tidy as this original
solution, so I'd still appreciate some advice:
1) What did I do wrong? Is
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.
My workaround right now is to have my Model create a helper object and use
manual
Would a modelmixin work for your situation?
http://www.tipfy.org/wiki/cookbook/reusing-models-with-modelmixin/
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To
I'd say that Guido just told us NOT to do the very thing that article is
advocating.
-Joshua
On May 4, 2011, at 7:30 PM, Calvin wrote:
Would a modelmixin work for your situation?
http://www.tipfy.org/wiki/cookbook/reusing-models-with-modelmixin/
--
You received this message because
