Antoine Pitrou solipsis at pitrou.net
Sat Mar 8 12:45:01 CET 2014

• Previous message: [Python-Dev] What is the precise problem? [was: Reference cycles in Exception.__traceback__]
• Next message: [Python-Dev] What is the precise problem? [was: Reference cycles in Exception.__traceback__]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sat, 8 Mar 2014 11:06:54 +0100
Victor Stinner <victor.stinner at gmail.com> wrote:
> 
> Attached script: never_deleted2.py, it's almost the same but it
> explains better the problem. The script creates MyObject and Future
> objects which are never deleted. Calling gc.collect() does *not* break
> the reference cycle (between the future, the exception, traceback and
> frames). Stopping the event loop does not remove Future nor MyObject
> objects. Only exiting Python does remove the Future object.

So clearly the coroutine must be kept alive by something.

Regards

Antoine.

---

• Previous message: [Python-Dev] What is the precise problem? [was: Reference cycles in Exception.__traceback__]
• Next message: [Python-Dev] What is the precise problem? [was: Reference cycles in Exception.__traceback__]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list