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 ncoghlan
Recipients docs@python, ncoghlan
Date 2013-09-19.08:03:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379577834.67.0.113922099701.issue19047@psf.upfronthosting.co.za>
In-reply-to
Content
I was just looking at weakref.finalize objects trying to figure out if they solve a problem I'm thinking about (they do), and I couldn't figure out from the class documentation ([1]) whether or not I needed to take care of keeping the object returned from weakref.finalize alive.

I don't (the module keeps finalizers alive automatically), but this critical piece of information is only mentioned in the example much further down in the documentation ([2]).

[1] http://docs.python.org/dev/library/weakref#weakref.finalize
[2] http://docs.python.org/dev/library/weakref#finalizer-objects

The 3.4 What's New should also explicitly mention weakref.finalize as an alternative to __del__ methods (perhaps as a comment in the section on PEP 422, perhaps just in the weakref section)
History
Date User Action Args
2013-09-19 08:03:54ncoghlansetrecipients: + ncoghlan, docs@python
2013-09-19 08:03:54ncoghlansetmessageid: <1379577834.67.0.113922099701.issue19047@psf.upfronthosting.co.za>
2013-09-19 08:03:54ncoghlanlinkissue19047 messages
2013-09-19 08:03:54ncoghlancreate