On Wed, 3 Jan 2007, Adam Olsen wrote: > That can be solved by moving the weakref to the stack frame -> exc > part, and only turning it from a strong reference into a weak > reference when the function exits. When debugging via the raised > exception, the chain of __context__ references would keep it alive.
That seems like a reasonable approach to me. The implementation might be tricky, but the behaviour sounds correct. -- ?!ng _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
