Mark, I've tried the last few days to get ActiveScript Debugging to work with ActivePython 2.1.211 / Win32all build 140. JIT Debugging (Invoking Visual Interdev / MS Script Debugger) on script runtime error / WSH Debugging switches doesn't work. Excactly nothing happens if you invoke WSH with cscript / wscript //X //D mypythontest.wsf. The python script is run but no debugger invoked. Same holds true for .pys files. Also trying to use PrimalScript 2.1 (great Script Editor / Environment) with debug script (which actually doesn only a wscript //X //D) doensn't work. Trying the same things with vbscript / jscript works perfectly. My study of ActriveScript debugging documentation showed that a script engine must at least implement and expose IActiveScriptDebug and IDebugStackFrameSniffer(Ex). VBScript / JScript actually do so. After getting the source of PyWin32 from CVS I saw that you actually implement these interfaces in your c / c++ code. But if I inspect the Active Python Scripting Engine in OleView the interfaces aren't exposed. VBScript / JScript behave differently. I' ve tested the debuging test in win32comext\axscript\test testHost4Dbg.py which seems to work, but I can't figure out why Script Debugger / Visual Interdev / JIT Debugging doesn't work. Regards -- Thomas Melzer --------------------------------------------------- bineo Network Solutions GmbH Germany EMail: [EMAIL PROTECTED] _______________________________________________ ActivePython mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/activepython
