[python-win32] Strange PythonWin IDE crash, now persistent

[Raefer Gabriel]

PythonWin has been working well for me as an IDE, until I started working
with wxPython, when I experienced a crash of PythonWin while trying to debug
a wxPython app.  After searching around, I've found that PythonWin might not
like having code from other toolkits running in its debugger.  While I
appreciate that, my problem is much worse: even after rebooting, every time
I try to start PythonWin, I now get the main PythonWin window with an empty
(no prompt) Interactive Window, and a modal error message window pops up
titled "Microsoft Visual C++ Runtime Library" with the contents: 

"Runtime Error! 

Program: C:\Python23\Lib\site-packages\pythonwin\Pythonwin.exe

This application has requested the Runtime to terminate it in an unusual
way.  Please contact the application's support team for more information."

When I click on the OK button, PythonWin closes down.

I tried uninstalling wxPython.  I tried uninstalling pywinall and
reinstalling.  I tried doing a full uninstall of Python 2.3, rebooting, and
reinstalling from scratch.  None of this makes any difference, I now get the
same error message EVERY time I try to start the PythonWin IDE.

I tried this on another computer as well, and had the exact same problem
after running the wxListCtrl sample through the debugger two or three times
and playing around with it a bit.  Sure enough, the same error message now
comes up every time, and the same attempts to remedy it fail.

Clearly something has persisted from the nasty wxPython/PythonWin
interaction that even a complete reinstall of Python and all python libs
hasn't fixed.  To tell you the truth, I don't understand how this is even
possible, unless some file that was not a part of my Python installation was
corrupted in a predictable fashion, or something ended up in the registry
that is causing this.  Anybody have any ideas?  At this point I'd be
satisfied with a fix that will give me back the ability to run PythonWin on
this computer, even if I never let it touch another line of wxPython code
again.  I'll use something else to work with my wxPython code if need be.

For the record, I'm running Python 2.3 final, with the latest Build 202
pywin32 extensions.  I was running the latest wxPython, 2.5.2.8 (I'd love to
try this with the stable wxPython 2.4.2.4 to see if I have the same problem,
but it's rather hard to test it again since I've gone through all my
immediately available computers here).

Thanks in advance,
Raefer Gabriel