Hello, I am in the process of migrating to PyPy and have a handful of unit test failing due to the different garbage collector and SQLAlchemy's usage of weak references in the Session identity map. Most failures are probably safe to ignore and all of them are fixed after manually calling gc.collect() somewhere in the test.
One specific failure though looks more worrying: a Session.rollback() call in the test's tearDown() method raises "InvalidRequestError: Can't attach instance `X`; another instance with key (<class `X`>, (8L, 1L)) is already present in this session." Before digging deeper, any idea on why it is triggered here and not in any other test? Is there another/better way to prevent it other than calling gc.collect() before Session.rollback() (and perhaps other Session operations)? More generally, are there any other known issues and caveats of running SQLAlchemy on PyPY? Thanks for any tip, George -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
