[Tutor] What has Editor X got that PyWin32 hasn't?
Jaggojaggo+Py at gmail.com
Thu Aug 14 12:29:17 CEST 2008
On Thu, Aug 14, 2008 at 7:20 AM, Dick Moores <rdm at rcblue.com> wrote:
> At 08:58 PM 8/13/2008, bob gailer wrote:
>> One thing I really like about Python Win is the integrated debugger, which
>> takes no time to start up. SPE OTOH uses WinPDB which runs as a separate
>> process that takes (in the demo video) 15 seconds to start (each time it is
>> requested)! Since I depend heavily on the debugger that delay would drive me
> Hm, I just measured how long Ulipad takes to get going with WinPDB, a
> plug-in: 20 seconds, but 10 seconds for a restart.
> Other than the time to start, could you compare debugging with Python Win
> and debugging with WinPDB?
> Dick Moores
Isn't that a bit system-dependent? PyWin starts for me in <5 seconds
on my spankin' new 2 gb ram, E8400 at 3 ghz.
SPE (the .pyw file) took ~7 seconds to start.
(Haven't WinPDB to test..)
More information about the Tutor