Gaëtan, Thanks for the tip. I wasn't able to reproduce the problem with r5200, but that doesn't necessarily mean that r5201 isn't the fix.
I've found that the trunk of sqlalchemy fixes the problem in my test case, but in my main development code exhibits a new CircularDependencyError, this time in IdentityManagedState: CircularDependencyError: Circular dependency detected [(<sqlalchemy.orm.identity.IdentityManagedState object at 0x031AC970>, <sqlalchemy.orm.identity.IdentityManagedState object at 0x035FA930>), (<sqlalchemy.orm.identity.IdentityManagedState object at 0x035FA930>, <sqlalchemy.orm.identity.IdentityManagedState object at 0x031AC970>)] [] I will be trying to create a minimal test case that reproduces this error now. I will follow up on the SQLAlchemy list; I'm just writing as a follow up to say thanks. Jason On Nov 19, 5:03 am, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote: > My guess is that this is a bug in SQLAlchemy, which depends on some > not-always-reproducible condition, such as the order of a normally > unordered collection (such as a dictionary) and the import modifies > that condition somehow. FWIW, I could reproduce the problem with SA > 0.4.8 (fromhttp://svn.sqlalchemy.org/sqlalchemy/tags/rel_0_4_8) but > not with SA trunk. And, most interestingly, changing the version > string of SA (not the acual version used!!!) from "svn" to "0.4.8" > fixes the problem... > > This is probably related to:http://www.sqlalchemy.org/trac/changeset/5201 > > Hope it helps, > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
