➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients Arfrever, DLitz, aliles, amaury.forgeotdarc, asvetlov, christian.heimes, georg.brandl, grahamd, gregory.p.smith, jcea, lemburg, neologix, pitrou, sbt, twouters, vstinner
Date 2013-10-21.20:47:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0E-+Rn1Aqb6uiUosFZQ5c7=gS1A0v4qPiRXu_8igi8=A@mail.gmail.com>
In-reply-to <1382381412.71.0.394561229043.issue16500@psf.upfronthosting.co.za>
Content 
> 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 ;-)
History
Date User Action Args
2013-10-21 20:47:56neologixsetrecipients: + neologix, lemburg, twouters, georg.brandl, gregory.p.smith, jcea, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, grahamd, Arfrever, asvetlov, sbt, aliles, DLitz
2013-10-21 20:47:56neologixlinkissue16500 messages
2013-10-21 20:47:56neologixcreate