its not always a list. the underlying storage could be a Set, or a dict. there is also a ticket to enhance the typing behavior in this regard, its #213. although even if we make subtypes that are specific to a collection type, actually subclassing "list" is somewhat inconvenient since its a proxying object (like we dont actually need the overhead of creating a native "list" instead of just "object"). it would also have to still contain inheritance to InstrumentedCollection (i.e. multiply inherit).
might you use duck-typing instead ? what happens if your code comes across a UserList (also not a list) ? On Mar 8, 8:37 pm, "kris" <[EMAIL PROTECTED]> wrote: > sqlalchemy.orm.attributes.InstrumentedList > > I was wondering why instrumentedList is derived from > 'object' instead of 'list'? > > I working with some introspection code and it fails > on attributes of type InstrumentedList because of this. > > Thanks, > kris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
