doing away with the __del__() thing ? what would we gain by
removing the __del__() call ? one thing I should do is insure ORM
etc. do not rely upon __del__() (which they shouldnt, although I just
tested with the AssertionPool and...surprise)
actually scratch that, the unit tests themselves call a bunch of
insert() and delete() executes for which they dont close the result set
(and therefore __del__ is what returns the connection in those cases).
If i remove the __del__ from pool.py, change line 69 of
test/orm/polymorph.py to close() the result of the table delete, and
then run the test with --mockpool (asserts only one connection used
throughout the app), all tests pass, which is a few dozen full blown
round trips through the mapper/session. so the ORM is closing
everything it opens.
8 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: is pool supposed to ...