Hi Again,
I'm also curious about use of dict_ versus getting from cls in
_as_declarative. IIRC, at pycon, you changed it so that DeclarativeMeta
passes the class's __dict__ as dict_ and then made it so that only dict_
is consulted for attributes.
However, _as_declarative intrinsically needs to futz with cls for things
like __mapper__, __table__ and __tablename__, which, iirc, was always
retrieved from cls, even before the declarative mixins stuff was done.
I'm wondering why _as_declarative doesn't just take a cls and it then
get everything from the cls itself?
I remember backwards compatability for some use that Grok makes of this,
but it should be a one-liner for them to change and 0.6 would seem like
a good boundary to do it...
What am I missing?
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.