[issue15412] Note in documentation for weakrefs

Changes by Richard Oudkerk : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue15412] Note in documentation for weakrefs

Roundup Robot added the comment: New changeset 78b0f294674c by Richard Oudkerk in branch '2.7': Issue #15412: Remove erroneous note about weakrefs http://hg.python.org/cpython/rev/78b0f294674c New changeset 24b13be81d61 by Richard Oudkerk in branch '3.2': Issue #15412: Remove erroneous note abou

[issue15412] Note in documentation for weakrefs

Antoine Pitrou added the comment: > I had assumed that since dead weakrefs were unhashable you couldn't > safely use them as keys in a dict. (Presumably removal of a no longer > hashable key from a dict is O(n)?) They are unhashable if you didn't hash them alive. Otherwise they retain their ol

[issue15412] Note in documentation for weakrefs

Richard Oudkerk added the comment: > The weakref is "dead" but it's still a weakref, and it can be used to > e.g. index a container of existing weakrefs (cf. WeakSet, > WeakKeyDictionary, WeakValueDictionary). Ah. I had assumed that since dead weakrefs were unhashable you couldn't safely use

[issue15412] Note in documentation for weakrefs

Antoine Pitrou added the comment: > In the documentation on weakrefs there is the following quote > > Note: Weak references to an object are cleared before the object’s > __del__() is called, to ensure that the weak reference callback > (if any) finds the object still alive. > > B

[issue15412] Note in documentation for weakrefs

New submission from Richard Oudkerk : In the documentation on weakrefs there is the following quote Note: Weak references to an object are cleared before the object’s __del__() is called, to ensure that the weak reference callback (if any) finds the object still alive. But I think