On 9/4/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
> Christopher Armstrong <[EMAIL PROTECTED]> writes:
>
> > I had the idea to create a fake Traceback object in Python that
> > doesn't hold references to any frame objects, but is still able to be
> > passed to 'raise' and formatted as tracebacks
Christopher Armstrong <[EMAIL PROTECTED]> writes:
> I had the idea to create a fake Traceback object in Python that
> doesn't hold references to any frame objects, but is still able to be
> passed to 'raise' and formatted as tracebacks are, etc. Unfortunately,
> raise does a type check on its thir
On 9/4/05, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 06:24 PM 9/3/2005 +1000, Christopher Armstrong wrote:
> >For example, perhaps a better idea would be to
> >change the traceback-printing functions to use Python attribute lookup
> >instead of internal structure lookup, and then change raise
At 06:24 PM 9/3/2005 +1000, Christopher Armstrong wrote:
>For example, perhaps a better idea would be to
>change the traceback-printing functions to use Python attribute lookup
>instead of internal structure lookup, and then change raise to accept
>arbitrary Python objects as its third argument, as
