Add connection checkout traceback to AssertionPool error message

Issue #2103 resolved
Former user created an issue

Attached patches (rel_0_6 and default) add a traceback to the AssertionPool error message, showing where the existing connection was checked out. This makes pooling issues easier to troubleshoot.

The patch turns this on by default (kw.pop('store_traceback', True)), so the traceback is stored on every checkout. That probably hurts performance, but AssertionPool shouldn't be used in production anyway.

Comments (6)

  1. Mike Bayer repo owner
    • changed milestone to 0.7.0

    pretty cool, do you need this in 0.6 ? this is more like "new feature / 0.7" kind of thing.

  2. Former user Account Deleted

    Doesn't hurt to include it if there's a 0.6.7 release, but it's no biggie to me (I can just run patched if I need it again while still on 0.6).

  3. Log in to comment