Re: [Sqlalchemy-tickets] [sqlalchemy] #2268: implement removal for SQLAlchemy events

[sqlalchemy <mi...@zz...>]

#2268: implement removal for SQLAlchemy events
---------------------------+---------------------------------------
      Reporter:  guest     |      Owner:  zzzeek
          Type:  task      |     Status:  new
      Priority:  medium    |  Milestone:  0.9.0
     Component:  engine    |   Severity:  very major - up to 2 days
    Resolution:            |   Keywords:
Progress State:  in queue  |
---------------------------+---------------------------------------
Changes (by zzzeek):

 * milestone:  0.x.xx => 0.9.0


Comment:

 a possible technique here could be that a target event listening function
 receives a collection (or some weak referencing association) that can
 point it to every ListenerCollection etc. which it is a part of, including
 some callable that can remove this event from that collection, taking into
 account whatever wrappers have been applied to it.   Any
 ListenerCollection that receives a new event would make sure this
 registration takes place.  If done consistently, this should account for
 all the many ways that a listener function gets assigned to many places,
 across subclasses, copies of dispatchers, etc. and not expose any of that
 to the removal process.

 tentative 0.9 assignment, we'll see if we get to it.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2268#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python