[Python-Dev] Reference cycles in Exception.__traceback__

[Guido van Rossum]

It's all very old C code that's deeply intertwined with interpreter
internals. Who knows what kind of assumptions are made by some of the C
code consuming frames and tracebacks...


On Thu, Mar 6, 2014 at 12:38 PM, Xavier Morel <python-dev at masklinn.net>wrote:

> On 2014-03-06, at 19:32 , Guido van Rossum <guido at python.org> wrote:
> > But inspect is in the stdlib. Surely changing inspect.py is less
> controversial than amending the semantics of frame objects.
>
> I've no idea, I'm just giving a case where I could have used the ability
> to create traceback objects even without the ability to create stack
> frames (changing the stdlib may also be an option, though I'd hope the
> explicit type checks were put in there for a reason)
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>



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