Hi Carl Friedrich, 

On Mon, Jun 14, 2010 at 15:21 +0200, Carl Friedrich Bolz wrote:
> Hi Holger,
> 
> On 06/14/2010 03:18 PM, holger krekel wrote:
> > related to the below issue: did you miss being able to say "--pdb"
> > on collection errors (import errors, syntax errors, errors during
> > code-execution-at-import time)?   Or the other way round: would you
> > mind if it did also enter the PDB prompt in that case?
> 
> I probably wouldn't mind, but I don't remember ever needing this.

Actually i just tried entering PDB on an import error and it seems
that locals/globals don't have meaningful values if the import fails.
So --pdb would not be of much use anyway. 
 
> While we are talking about --pdb: what kind of bugs me is that xfailing 
> tests drop into a debugger when they fail. I already *know* about this 
> failure, so usually I don't want that.

sure, thanks for reporting.  i just fixed this in py-trunk, also unified
traceback reporting between --pdb and non-pdb mode. 

best,
holger
_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev

Reply via email to