On Fri, 2006-01-27 at 16:38 -0700, Shane Hathaway wrote:
> It's checked in, but perhaps there is some other code that also needs to
> use the custom traceback formatter. The conversion is trivial. Replace
> this:
>
>from traceback import print_exception
>print_exception(...)
>
> with
Christian Theune wrote:
On Fri, 2006-01-27 at 18:46 -0200, Sidnei da Silva wrote:
On Fri, Jan 27, 2006 at 09:37:03PM +0100, Christian Theune wrote:
| Is it intentional that there is a distinction? It took me quite a while
| to actually notice that minore difference and come to the conclusion
|
Hi,
On Fri, 2006-01-27 at 20:34 +0100, Christian Theune wrote:
> Obviously I'm blind. I found the __traceback_info__ code a few lines
> down.
>
> Obviously they are used for slightly different things.
>
> Obviously I'm going to investigate again, why the __traceback_info__
> elements don't appe
On Fri, 2006-01-27 at 18:46 -0200, Sidnei da Silva wrote:
> On Fri, Jan 27, 2006 at 09:37:03PM +0100, Christian Theune wrote:
> | Is it intentional that there is a distinction? It took me quite a while
> | to actually notice that minore difference and come to the conclusion
> | that there are two d
On Fri, Jan 27, 2006 at 09:37:03PM +0100, Christian Theune wrote:
| Is it intentional that there is a distinction? It took me quite a while
| to actually notice that minore difference and come to the conclusion
| that there are two different mechanisms used.
There's a proposal from Shane Hathaway
Obviously I'm blind. I found the __traceback_info__ code a few lines
down.
Obviously they are used for slightly different things.
Obviously I'm going to investigate again, why the __traceback_info__
elements don't appear.
Mea culpa,
Christian
--
gocept gmbh & co. kg - forsterstraße 29 - 06112
