Lines Matching refs:__del__

4 The basic rule for dealing with weakref callbacks (and __del__ methods too,
45 weakref callback or __del__ method does something nasty on purpose:  as
152  is breaking cycles.  If an object with a __del__ method is not itself in
154  matter of course, drop the refcount on that object to 0, and its __del__
186 with __del__ methods, refusing to collect them, appending them to gc.garbage
190     There's a big difference between __del__ and weakref callbacks.
191     The __del__ method is "internal" to a design.  When you design a
195     Now, suppose you have a design that makes has no __del__ methods but
203 IOW, a class designer can out-think __del__ problems, but has no control
210 __del__ methods is to avoid running finalizers in an arbitrary order).
218  them.  People simply shouldn't try to use __del__ or weakref callbacks to