Author zzzeek
Recipients JohanAR, itamarst, rhettinger, sbt, tim.peters, zzzeek
Date 2016-09-08.21:59:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473371992.46.0.907450479715.issue14976@psf.upfronthosting.co.za>
In-reply-to
Content
SQLAlchemy suffered from this issue long ago as we use a Queue for connections, which can be collected via weakref callback and sent back to put(), which we observed can occur via gc.    For many years (like since 2007 or so) we've packaged a complete copy of Queue.Queue with an RLock inside of it to work around it.

I'm just noticing this issue because I'm writing a new connection pool implementation that tries to deal with this issue a little differently (not using Queue.Queue though).
History
Date User Action Args
2016-09-08 21:59:52zzzeeksetrecipients: + zzzeek, tim.peters, rhettinger, sbt, JohanAR, itamarst
2016-09-08 21:59:52zzzeeksetmessageid: <1473371992.46.0.907450479715.issue14976@psf.upfronthosting.co.za>
2016-09-08 21:59:52zzzeeklinkissue14976 messages
2016-09-08 21:59:52zzzeekcreate