Odd problem with Wing IDE & PythonForDelphi extensions

Neil Hodgson nhodgson at bigpond.net.au
Sat Nov 9 16:47:14 EST 2002


animeshk:

> "Error: The debug connection closed unexpectedly while waiting for
> reply type 0x1011 after message type 0x70001:
> Runtime failure details:
> Exception: socket.error
> Value = (10054, 'winsock error')
>
> Of course, I'm not using winsock at all.

    I can't help much but can explain it a bit. Wing IDE runs programs being
debugged in a separate process and uses sockets to talk to a debugger stub
in the process. PythonWin runs programs in its own process and so does not
use sockets for debugging. In general the separate process approach is
better as you get a clean environment for every run whereas PythonWin often
retains remnants from previous program runs.

> I realize that this isn't enough information: if anyone would like the
> source for the DLL, for testing, let me know.
>
> Does anyone know what this might mean?  Is this a Wing IDE bug?

   Wing IDE has a support forum at
http://wingide.com/support/forum
   and an alarmingly large amount of debugger documentation at
http://wingide.com/psupport/wingide-1.1/node7.html

   Neil





More information about the Python-list mailing list