Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #77769 > unrolled thread
| Started by | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| First post | 2014-09-11 00:37 -0600 |
| Last post | 2014-09-11 00:37 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: recursive closure Ian Kelly <ian.g.kelly@gmail.com> - 2014-09-11 00:37 -0600
| From | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| Date | 2014-09-11 00:37 -0600 |
| Subject | Re: recursive closure |
| Message-ID | <mailman.13926.1410417518.18130.python-list@python.org> |
On Wed, Sep 10, 2014 at 10:00 PM, Li Tianqing <jazeltq@163.com> wrote: > gc.set_debug(gc.DEBUG_LEAK) The DEBUG_LEAK flag implies the DEBUG_SAVEALL flag, which causes all unreachable objects to be appended to gc.garbage rather than freed. https://docs.python.org/3/library/gc.html#gc.DEBUG_SAVEALL Try not setting the flag, and I think you will find that gc.garbage no longer accumulates.
Back to top | Article view | comp.lang.python
csiph-web