Charles-François Natali added the comment: > Well it is customary for callback-based APIs to hold strong references to > their callbacks. If a library wants to avoid leaks, it should register a > single callback which will then walk the current "live" resources and protect > them.
I guess that the custom usage makes sense. I'd just like a note in the doc, if possible ;-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16500> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
