A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Reference cycles in Exception.__traceback__

[Python-Dev] Reference cycles in Exception.__traceback__ [Python-Dev] Reference cycles in Exception.__traceback__Yury Selivanov yselivanov.ml at gmail.com
Thu Mar 6 16:03:09 CET 2014
On 2014-03-06, 8:42 AM, Antoine Pitrou wrote:
> Le 05/03/2014 23:53, Nick Coghlan a écrit :
>>
>> __traceback__ wouldn't change [...]
>
> Uh, really? If you want to suppress all reference cycles, you *have* 
> to remove __traceback__.
>
> The problem is to make computation of the traceback summary 
> lightweight enough that it doesn't degrade performance in the common 
> case where you don't have to print the traceback later.

So why can't we allow instantiation of types.TracebackType &
types.FrameType?

It should be about the same time to reconstruct traceback and
its frames without locals, as to create named tuples.


Yury
More information about the Python-Dev mailing list

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