Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/132933.html below:

[Python-Dev] Reference cycles in Exception.__traceback__

• Previous message: [Python-Dev] Reference cycles in Exception.__traceback__
• Next message: [Python-Dev] Reference cycles in Exception.__traceback__
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Le 05/03/2014 17:37, Victor Stinner a écrit :
>
> Python 3.4 introduced frame.clear(), but frame.clear() raises an
> RuntimeError if the frame is still running. And it doesn't break all
> reference cycles.
>
> An obvious workaround is to store the traceback as text, but this
> operation is "expensive" especially if the traceback is only needed in
> rare cases.

Another "obvious" workaround is to call frame.clear() from the parent 
function (i.e. have a dedicated wrapping layer).

Regards

Antoine.

• Previous message: [Python-Dev] Reference cycles in Exception.__traceback__
• Next message: [Python-Dev] Reference cycles in Exception.__traceback__
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4