[Python-Dev] What is the precise problem? [was: Reference cycles in Exception.traceback] (original) (raw)

Guido van Rossum guido at python.org
Mon Mar 10 18:35:36 CET 2014

On Mon, Mar 10, 2014 at 10:30 AM, Maciej Fijalkowski <fijall at gmail.com>wrote:

On Mon, Mar 10, 2014 at 3:23 PM, Victor Stinner <victor.stinner at gmail.com> wrote: > 2014-03-10 13:11 GMT+01:00 Maciej Fijalkowski <fijall at gmail.com>: >> It was agreed long time ago that the immediate finalization is an >> implementation specific detail and it's not guaranteed. You should not _>> rely on del_s being called timely one way or another. Why would you >> require this for the program to work correctly in the particular >> example of traceback? > > For asyncio, it's very useful to see unhandled exceptions as early as > possible. Otherwise, your program is blocked and you don't know why. > > Guido van Rossum suggests to run gc.collect() regulary: > http://code.google.com/p/tulip/issues/detail?id=42 > > Victor

twisted goes around it by attaching errback by hand. Would that work for tulip?

Can you describe that idea in more detail?

-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140310/0c29cb9c/attachment.html>

More information about the Python-Dev mailing list