[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2014-07-19 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2014-05-27 Thread Xavier de Gaye
Xavier de Gaye added the comment: Yes the patch does change the semantics of the quit command: * no change when pdb is run as a script or with 'python -m pdb script_name'. As stated in the doc, the 'quit command': "Quit from the debugger. The program being executed is aborted." * but

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2014-05-27 Thread Richard Marko
Richard Marko added the comment: Would be nice to have this commited as without this change -if self.quitting: -return # None +if not self.botframe: +self.botframe = frame it's not possible to quit Bdb (and the code it's executing) as it just returns and

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2013-02-25 Thread Xavier de Gaye
Xavier de Gaye added the comment: The patch changes the semantics of the quit command: quit behaves like the gdb detach command when pdb is started with set_trace. -- Added file: http://bugs.python.org/file29232/branch-27.patch ___ Python tracker

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2013-02-25 Thread Xavier de Gaye
Xavier de Gaye added the comment: There is an error in my patch (already fixed in pdb-clone) and in Jyrki's patch. Running Jyrki's patch on quit.py produces the following output where the line number in the last entry of the backtrace is incorrect (should be line 9 instead of line 7): $ python q

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2013-02-23 Thread Jyrki Pulliainen
Jyrki Pulliainen added the comment: I took Xavier's patch and ported in on the 2.7. It'll probably go as is for 3.2. The functionality seems to be working and tests pass. -- keywords: +patch nosy: +nailor Added file: http://bugs.python.org/file29208/issue16446.patch _

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2013-02-21 Thread Giampaolo Rodola'
Giampaolo Rodola' added the comment: I also bumped into this problem on both 2.7 and 3.3. It is very annoying. -- ___ Python tracker ___ _

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2013-02-21 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2012-11-24 Thread Xavier de Gaye
Xavier de Gaye added the comment: See how this is fixed at http://code.google.com/p/pdb-clone/source/detail?r=8bbac1ffee749fcfd96ea3a2aaca1f240cafc2cc -- ___ Python tracker ___ _

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2012-11-15 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- versions: +Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2012-11-15 Thread Andrew Svetlov
Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue16446] pdb raises BdbQuit on 'quit' when started with set_trace

2012-11-08 Thread Xavier de Gaye
New submission from Xavier de Gaye: Also, the two oldest frames of the stack are identical (sic), according to the printed traceback. $ python3 foo.py > /tmp/foo.py(3)() -> x = 1 (Pdb) import sys; print(sys.version) 3.2.2 (default, Dec 27 2011, 17:35:55) [GCC 4.3.2] (Pdb) list 1 import pd