En Tue, 29 May 2007 15:13:33 -0300, George Sakkis
<[EMAIL PROTECTED]> escribió:
> On May 29, 1:21 pm, "Gabriel Genellina" <[EMAIL PROTECTED]>
> wrote:
>> A traceback contains a linked list of frames, each with its own globals
>> and locals and lot of context info.
>> I'm not sure that moving a t
On May 29, 1:21 pm, "Gabriel Genellina" <[EMAIL PROTECTED]>
wrote:
> En Tue, 29 May 2007 13:51:09 -0300, George Sakkis
> <[EMAIL PROTECTED]> escribió:
>
> > The traceback module is handy if you want a text representation of the
> > traceback, not the actual traceback. The reason I want to store the
En Tue, 29 May 2007 13:51:09 -0300, George Sakkis
<[EMAIL PROTECTED]> escribió:
> The traceback module is handy if you want a text representation of the
> traceback, not the actual traceback. The reason I want to store the
> actual traceback is to make the exception transparent to the user,
> i.
On May 29, 9:46 am, [EMAIL PROTECTED] wrote:
> On May 28, 10:46 pm, George Sakkis <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'm reading the docs on sys.exc_info() but I can't tell for sure
> > whether I'm using it safely to get a snapshot of an exception and
> > reraise it later. The use case is a class
On May 28, 10:46 pm, George Sakkis <[EMAIL PROTECTED]> wrote:
> I'm reading the docs on sys.exc_info() but I can't tell for sure
> whether I'm using it safely to get a snapshot of an exception and
> reraise it later. The use case is a class which acts like a deferred
> callable, a callable that wil
I'm reading the docs on sys.exc_info() but I can't tell for sure
whether I'm using it safely to get a snapshot of an exception and
reraise it later. The use case is a class which acts like a deferred
callable, a callable that will be called at some point in the future
(possibly in a different threa
