[Sqlalchemy-tickets] Issue #4255: break out pool into a package; include prioritypool? (zzzeek/sqlalchemy)

[Michael B. <iss...@bi...>]

New issue 4255: break out pool into a package; include prioritypool?
https://bitbucket.org/zzzeek/sqlalchemy/issues/4255/break-out-pool-into-a-package-include

Michael Bayer:

There's enough attention going on with the connection pool these days that it might be nice to break it into a package, such that the main Pool/ConnectionFairy/ConnectionRecord is in one place, the ancient/never-used/crufty "manage" stuff can be elsewhere (and probably deprecated), and then the implementation classes like QueuePool, SingletonThreadPool can each get their own file and be kind of manageable.  Then we can think about evaluating haalchemy's pool https://bitbucket.org/zzzeek/haalchemy/src/master/haalchemy/clients/sqlalchemy/pool.py for inclusion as well.   For AbstractPriorityPool it still might be nice to have the "queue" part of it broken out into a separate class so that it can be more easily compared to QueuePool.