:59, Bruno Desthuilliers wrote:
> Agustin Villena a écrit :
>
>
>
> > On May 22, 5:19 am, Bruno Desthuilliers > [EMAIL PROTECTED]> wrote:
> >> Agustin Villena a écrit :
>
> >>>> And not that useful - why would one care about the function being
>
On May 22, 5:19 am, Bruno Desthuilliers wrote:
> Agustin Villena a écrit :
>
> >> And not that useful - why would one care about the function being
> >> defined in class X or Y when one have the exact file and line ?
>
> > I have 3 reasons:
>
> > 1) M
On 20 mayo, 12:10, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote:
> En Mon, 19 May 2008 10:54:05 -0300, Agustin Villena
> <[EMAIL PROTECTED]> escribió:
>
> > On May 18, 4:31 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> >> Agust
> And not that useful - why would one care about the function being
> defined in class X or Y when one have the exact file and line ?
I have 3 reasons:
1) My developing time is expended running unit tests and browsing
tracebacks to find which is the real problem. Knowing the offender
class (inst
On May 18, 4:31 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> Agustin Villena schrieb:
>
>
>
> > Hi!
>
> > is there anyway to show the class of amethodin an exception's
> > traceback?
>
> > For example, the next code
>
Hi!
is there anyway to show the class of a method in an exception's
traceback?
For example, the next code
class Some(object):
def foo(self,x):
raise Exception(x)
obj = Some()
obj.foo("some arg")
produces the next traceback
Traceback (most recent call last):
File "", line 231, in
