Message61071
Here are comments from Guido, taken from a patch
report that's been closed:
"""
In a discussion before lunch, Tim suggested that when
Python exits (or better, in Py_Finalize()) a check
could be made if there is any garbage in gc.garbage,
and if so, a warning about this should be printed to
stderr. That seems a nice feature.
In that same discussion, I realized that the module
cleanup behavior (where all globals in a module are
set to None when the module object is deallocated) is
probably no longer necessary now that we have GC.
"""
The point to #1 is that we let objects in unreachable
cycles leak when they have __del__ methods. While we
give the user ways to know about that and to clean
them up (via exposing the trash in gc.garbage), a non-
expert user (or an expert who simply isn't thinking
about this -- whatever, you don't know unless you
specifically look for it) may never know that they're
leaking. |
|
Date |
User |
Action |
Args |
2008-01-20 09:59:15 | admin | link | issue477863 messages |
2008-01-20 09:59:15 | admin | create | |
|