On Tuesday, May 12, 2015 at 10:06:57 AM UTC-5, Michael Bayer wrote:
On 5/12/15 9:34 AM, Jonathon Nelson wrote:
I'm working on an application where I want to use one and only one
connection, even in the face of errors.
Originally I used AssertionPool, but it seemed to misbehave
On 5/14/15 12:43 PM, Jonathon Nelson wrote:
And indeed you are correct. However, this comes as quite a surprise to me.
As an idiom:
try:
do_stuff()
except SomeError, e:
make_some_noise(e)
maybe_return_here_etc
is a pretty common idiom. I tried deleting 'e' within the except
On Tue, May 12, 2015 at 9:28 AM, Mike Bayer mike...@zzzcomputing.com
wrote:
On 5/12/15 9:34 AM, Jonathon Nelson wrote:
I'm working on an application where I want to use one and only one
connection, even in the face of errors.
Originally I used AssertionPool, but it seemed to misbehave
I'm working on an application where I want to use one and only one
connection, even in the face of errors.
Originally I used AssertionPool, but it seemed to misbehave sometimes in
the face of a disconnection.
Switching to QueuePool, I somewhat surprisingly got the same result.
This is how I
On 5/12/15 9:34 AM, Jonathon Nelson wrote:
I'm working on an application where I want to use one and only one
connection, even in the face of errors.
Originally I used AssertionPool, but it seemed to misbehave sometimes
in the face of a disconnection.
Switching to QueuePool, I somewhat
