[py-dev] another traceback cut weirdness

[holger krekel]

Hi Ronny,

On Mon, Jan 18, 2010 at 16:14 +0100, Ronny Pfannschmidt wrote:
> i just noticed that traceback.cut will return a traceback
> with all other filtering undone again
> since it passes a raw traceback entry into the Traceback ctor.
> 
> is there any deeper reason for that or did it just work, cause cutting
> always was first

probably. The whole machinery was done for py.test which obviously
invokes it in a certain way. 

> if its not intentional i could add a .filter(lambda entry: entry in
> self) to get it solved

Sounds ok although i am not sure it's that easy.  Let's maybe 
continue any more discussion off-list as i guess not too many 
people here are interested in the details ... 

cheers,
holger