Re: [Sqlalchemy-tickets] [sqlalchemy] #2536: ResourceClosedError can sometimes be raised instead of
Brought to you by:
zzzeek
From: sqlalchemy <mi...@zz...> - 2012-07-20 03:46:37
|
#2536: ResourceClosedError can sometimes be raised instead of more appropriate OperationalError -----------------------------------+------------------------------------ Reporter: jerdfelt | Owner: Type: defect | Status: closed Priority: medium | Milestone: Component: access | Severity: no triage selected yet Resolution: invalid | Keywords: Progress State: completed/closed | -----------------------------------+------------------------------------ Changes (by zzzeek): * status: new => closed * resolution: => invalid * status_field: awaiting triage => completed/closed Comment: looks great, and I've added myself as a monitor on the issue. I sincerely hope they respond, though looking at the level of inactivity on MySQLdbs tracker has me concerned. -- Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2536#comment:8> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |