- changed milestone to 0.7.xx
- marked as task
- marked as major
- changed title to implement removal for SQLAlchemy events
- changed component to engine
implement removal for SQLAlchemy events
No description provided.
Comments (4)
-
repo owner -
repo owner - changed milestone to 0.9.0
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.
-
repo owner - changed status to resolved
-
repo owner - removed milestone
Removing milestone: 0.9.0 (automated comment)
- Log in to comment
removal of events is not implemented right now. (note its not in the docs)