heisenbug in aisle 3

(when db.dispose is called in unitofwork test with sqlite, the first test that runs in memusage grows by two gc'ed objects on every iteration; then the problem vanishes.  doesnt matter what test runs in memusage.  doing a dispose() in memusage solves the problem also.  screwing wiht the mechanics of engine.dispose() only fix it when both the pool.dispose() *and* the pool.ressurect() are disabled.  its just a subtle python/pysqlite bug afaict)

diff --git a/test/orm/unitofwork.py b/test/orm/unitofwork.py
index ee696cd9d47959d5a792249ecc3d3d798e78b7f2..36222472d52f00c85a41c4e20757a2dcc9e85b01 100644 (file)
--- a/test/orm/unitofwork.py
+++ b/test/orm/unitofwork.py
@@ -2024,6 +2024,7 @@ class TransactionTest(ORMTest):
         # todo: on 8.3 at least, the failed commit seems to close the cursor?
         # needs investigation.  leaving in the DDL above now to help verify
         # that the new deferrable support on FK isn't involved in this issue.
-        t1.bind.engine.dispose()
+        if testing.against('postgres'):
+            t1.bind.engine.dispose()
 if __name__ == "__main__":
     testenv.main()