You are right, reference cycles with __del__ methods are treated differently from reference cycles without __del__ methods. The former are uncollectable in Python 2.
On Sunday, February 1, 2015 at 12:00:13 PM UTC-5, Nils Bruin wrote: > So indeed, the running of __del__ methods is not guaranteed. The > recommended way to ensure resources are released in a timely fashing is via > try/finally. Thats true in plain Python, in Cython you can also use RAII. An interesting test would be to add a check that there are no unreachable objects after running the doctests (gc.garbage should be empty) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
