Traceback disapears before I can read it!

[John Ladasky]

"Edward K. Ream" <edreamleo at charter.net> wrote in message news:<vbtf7chjoe6r78 at corp.supernews.com>...
> > Of course, I still need to see a traceback to debug my programs.  If I
> > invoke my wxPython app using PYTHON.EXE, I can get a stdout window,
> > which prints the traceback and any print statements that I might
> > include in my program.  So far, so good.  However, if an error
> > actually occurs the stdout window closes immediately after printing
> > the traceback.
> 
> Invoke Python with the -i argument so that Python stays in interactive mode
> after your script exits.  For example, on XP, in the Settings:Folder option
> dialog, set the open option for .py files to:
> 
> C:\PYTHON22\python.exe -i "%1" %*

Thanks, Ed.  That gets me most of what I'm looking for.

--
John J. Ladasky Jr., Ph.D.
Department of Biology
Johns Hopkins University
Baltimore MD 21218
USA
Earth