Looks like something related to deserializing without mappers set up, or deserializing into an environment where the class structure and/or mappers are not configured the same way. This is usually not the way that manifests itself, though. The key would be the change that started causing the issue. If you want to pdb into the mechanics of _new_state_if_none it might become apparent what the mismatch is - I can't do much without being shown how to reproduce it exactly.
Any more specifics/details/reproducing cases here would shed more light. On Oct 28, 2011, at 12:30 PM, Burak Arslan wrote: > hi, > > any ideas on what could be the cause of the following backtrace here? > https://gist.github.com/1322636#comments. this is probably something > i'll need to fix in rpclib code, but I don't see what causes this. > > sqlalchemy version is latest trunk from today. the backtrace is one line > off because of a comment, no change in source code around there. > > thanks, > burak > > -- > 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 > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
