Comment 3 for bug 487076

I tested with 0.3.1 and 0.3.4(from goolge code) tar versions and got same issue.
The versions 0.3.1 and 0.3.4 creates a new connection id for each thread and kill inactive (and sometimes random kill an active) connection when the method PySQLPool.cleanupPool() is called.
I follow your advice and get the last truk version and notice a different behavior. The lastest trunk check out create one connection for all threads. It appears to be stable and thread safe. I notice no issues when PySQLPool.cleanupPool() method is called.