summaryrefslogtreecommitdiff
path: root/Python/pyarena.c
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2006-04-15 01:48:57 +0000
committerTim Peters <tim.peters@gmail.com>2006-04-15 01:48:57 +0000
commit7f098112ee89a250862dcd48f157a4ab3522fb54 (patch)
tree2121ba92314236e8b87b105cd9686ee85e754ed4 /Python/pyarena.c
parent8ebb28df3a6e0bce240b6c2aa20d7aa5a4dfef39 (diff)
downloadcpython-git-7f098112ee89a250862dcd48f157a4ab3522fb54.tar.gz
Changed comments to make sense now that the LazyList-based
examples no longer require any explicit closing to avoid leaking. That the tee-based examples still do is (I think) still a mystery. Part of the mystery is that gc.garbage remains empty: if it were the case that some generator in a trash cycle said it needed finalization, suppressing collection of that cycle, that generator _would_ show up in gc.garbage. So this is acting more like, e.g., some tp_traverse slot isn't visiting all the pointers it should (in which case the skipped pointer(s) would act like an external root, silently suppressing collection of everything reachable from it(them)).
Diffstat (limited to 'Python/pyarena.c')
0 files changed, 0 insertions, 0 deletions