Debugger fails upon GeneratorExit exception about pyscripter HOT 8 CLOSED

Works correctly with remote engines.  Will be fixed for the internal engine.

This seems to be fixed in 1.8.5.

It still happens to me with the internal debugger.  It seems that this a Python 
bdb
issue.  For example PythonWin has the same problem.

Resolution.  Use remote debugger.  Cannot fix.

I think this is a fixable problem, because I don't believe it happens in the 
Wingware
Python debugger. In fact, I installed and used Wingware to identify the bug here
since I couldn't debug in PyScripter.

Why did you have to use Wing since the PyScripter remote engine should do just 
fine?

I did some more investigation and here are the findings:
Interestingly, the following code seems to work well when debugging with the 
internal
engine:
def f():
    a = (a for a in ())
    del a
    print "hey"

f()


Then I tried to use the standard Python Interpeter and pdb.
So I have the following modules in a directory:
a) module2.py
a = (a for a in ())
del a
print "hey"

b) module3.py
def f():
    import module2

I start python.exe from the same directory as the above modules and here is the
commands issued and the results I got:
==============================================================================
C:\Temp>"c:\Program Files\Python25\python"
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import module3
>>> import pdb
>>> pdb.run('module3.f()')
> <string>(1)<module>()
(Pdb) s
--Call--
> c:\temp\module3.py(1)f()
-> def f():
(Pdb) s
> c:\temp\module3.py(2)f()
-> import module2
(Pdb) s
--Call--
> c:\temp\module2.py(1)<module>()
-> a = (a for a in ())
(Pdb) s
> c:\temp\module2.py(1)<module>()
-> a = (a for a in ())
(Pdb) s
> c:\temp\module2.py(2)<module>()
-> del a
(Pdb) s
--Call--
c:\Program Files\Python25\lib\bdb.py:318: RuntimeWarning: tp_compare didn't retu
rn -1 or -2 for exception
  i = max(0, len(stack) - 1)
hey
>>>
================================================================================
=

So the standard Python interpreter and pdb fails on the above script.  This is 
why I
was saying that this is not a PyScripter problem.  Moreover,if you google on
"RuntimeWarning: tp_compare" you will see that this is a recurring problem 
affecting
many python modules.

As a conclusion until this is fixed in Python use the remote Python engine in 
Pyscripter.