Issue 634116: pdb quit breakage (original) (raw)
Issue634116
Created on 2002-11-05 22:26 by gvanrossum, last changed 2022-04-10 16:05 by admin. This issue is now closed.
| Messages (3) | ||
|---|---|---|
| msg13099 - (view) | Author: Guido van Rossum (gvanrossum) *  |
Date: 2002-11-05 22:26 |
| Behold: >>> import pdb >>> pdb.run("pass") > (1)?() (Pdb) q >>> pdb.run("pass") Traceback (most recent call last): File "", line 1, in ? File "/usr/local/lib/python2.3/bdb.py", line 48, in trace_dispatch return self.dispatch_line(frame) File "/usr/local/lib/python2.3/bdb.py", line 61, in dispatch_line if self.quitting: raise BdbQuit bdb.BdbQuit >>> pdb.run("pass") > (1)?() (Pdb) q >>> IOW, quitting out of pdb causes some sticky state to remain behind which sabotages the next call to pdb.run(). This bug is new in Python 2.3. | ||
| msg13100 - (view) | Author: Michael Stone (mbrierst) | Date: 2003-01-31 20:57 |
| Logged In: YES user_id=670441 This is very odd. I just downloaded the latest cvs and do not see the problem. Is it still there? | ||
| msg13101 - (view) | Author: Guido van Rossum (gvanrossum) * |
Date: 2003-01-31 21:07 |
| Logged In: YES user_id=6380 WFM too now. Maybe the latest checkin (by mwh) to pdb.py fixed it. |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:05:49 | admin | set | github: 37426 |
| 2002-11-05 22:26:52 | gvanrossum | create |