[issue1294] Management of KeyboardInterrupt in cmd.py

Philip Zerull added the comment: Hello, Being of a similar mindset to draghuram on the do_KeyboardInterrupt idea and thought I'd implement it as a subclass. While this probably wasn't fully implemented correctly, I think it provides an interesting solution to stephbul's frustrations and won

[issue1294] Management of KeyboardInterrupt in cmd.py

Garrett Cooper added the comment: I realize that this bug is closed, but I just had a comment to make. Handling EOF is simple: def do_EOF(self, arg): pass For my purposes I want to raise an EOFError so I can trickle up the chain to the appropriate caller because I'm coding a CLI where I

[issue1294] Management of KeyboardInterrupt in cmd.py

Guido van Rossum added the comment: I don't think this is a good idea. -- resolution: -> rejected status: open -> closed ___ Python tracker ___ _

[issue1294] Management of KeyboardInterrupt in cmd.py

Changes by Guido van Rossum : Removed file: http://bugs.python.org/file8578/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: > I am not sure I understand: currently Ctrl-C generates a > KeyboardInterrupt, which can be caught by the application which can > then decide how to proceed (in particular it can start another command > loop or exit with a meaningful message or anything

[issue1294] Management of KeyboardInterrupt in cmd.py

Ilya Sandler added the comment: > But currently, CTRL-C terminates the session instead of propagating upstream I am not sure I understand: currently Ctrl-C generates a KeyboardInterrupt, which can be caught by the application which can then decide how to proceed (in particular it can start an

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: On Sun, Nov 8, 2009 at 8:22 PM, Ilya Sandler wrote: > Is not this patch backward incompatible? > > E.g any cmd-based application which expects Ctrl-C to propagate to the > top level will be broken by this patch. But currently, CTRL-C terminates the sess

[issue1294] Management of KeyboardInterrupt in cmd.py

Ilya Sandler added the comment: Is not this patch backward incompatible? E.g any cmd-based application which expects Ctrl-C to propagate to the top level will be broken by this patch. As for pdb, I don't think pdb will benefit from this patch: as I believe that pdb needs something along the li

[issue1294] Management of KeyboardInterrupt in cmd.py

Changes by Daniel Diniz : -- stage: -> test needed versions: +Python 2.7, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Python-bug

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: > I've added developer status to your username. Let me know if it doesn't > work. It does. Thanks. __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1294] Management of KeyboardInterrupt in cmd.py

Guido van Rossum added the comment: I've added developer status to your username. Let me know if it doesn't work. __ Tracker <[EMAIL PROTECTED]> __ ___ P

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: Ok. BTW, can I get tracker permissions? I will try to check old bugs to update their information and if required, close them. __ Tracker <[EMAIL PROTECTED]>

[issue1294] Management of KeyboardInterrupt in cmd.py

Guido van Rossum added the comment: To mark things for the bugday, set the 'easy' keyword. However, this particular one is IMO too subtle for a bugday, witness the discussion here. Perhaps a bugday could come up with an ultimate patch, but I'd be hesitant to submit it without having reviewed it

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: bugday task? __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: "Tomorrow" took a while to come by :-) With out the patch, pdb prints this on Ctrl-C: "KeyboardInterrupt Uncaught exception. Entering post mortem debugging Running 'cont' or 'step' will restart the program" With the patch, pdb prompt appears again. Ctrl-

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: > I will look into this for 2.6. No promises. Somebody ought to check > whether this does not cause problems for pdb. Thanks. I will check about pdb tomorrow. __ Tracker <[EMAIL PROTECTED]>

[issue1294] Management of KeyboardInterrupt in cmd.py

Guido van Rossum added the comment: I will look into this for 2.6. No promises. Somebody ought to check whether this does not cause problems for pdb. -- resolution: rejected -> status: closed -> open versions: +Python 2.6 -Python 2.5 __ Tracker <[EMAIL

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: My patch adds very sensible default behaviour when Ctrl-C or Ctrl-D are entered. It follows the tradition of many unix programs such as bash and bc which exit on Ctrl-D and ignore Ctrl-c in one way or another. Most importantly, a user can always override th

[issue1294] Management of KeyboardInterrupt in cmd.py

Alexandre Vassalotti added the comment: First, I would like to say thank you both for spending your time trying to do a contribution to Python. However, I believe the current behavior of cmd.py is correct. The module documentation states clearly that "End of file on input is processed as the com

[issue1294] Management of KeyboardInterrupt in cmd.py

BULOT added the comment: Well, I made it with a diff -ruN, it works fine on my ubuntu. It is only a ctrl-C management only, not a ctrl-D. What do you mean by broken? Regards. Stephbul 2007/10/19, Guido van Rossum <[EMAIL PROTECTED]>: > > > Guido van Rossum added the comment: > > Hmm... I don't

[issue1294] Management of KeyboardInterrupt in cmd.py

Raghuram Devarakonda added the comment: I tested cmd.py on Linux and two things (including the one reported by OP) looked odd to me. 1) CTRL-D produces a message "*** Unknown syntax: EOF". 2) CTRL-C produces a KeyboardInterrupt exception and the session terminates. I am attaching a patch that

[issue1294] Management of KeyboardInterrupt in cmd.py

Guido van Rossum added the comment: Hmm... I don't think this is the right thing to do. The code is broken in several ways. I recommend you find someone to help you come up with a better patch in comp.lang.python. -- keywords: +patch __ Tracker <[EMAIL

[issue1294] Management of KeyboardInterrupt in cmd.py

BULOT added the comment: Hello, Here is my patch for cmd.py Regards stephbul Added file: http://bugs.python.org/file8566/cmd.py.keyboardinterrupt.patch __ Tracker <[EMAIL PROTECTED]> __--- backuo

[issue1294] Management of KeyboardInterrupt in cmd.py

Guido van Rossum added the comment: Would you mind submitting a patch instead of a whole new file? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __ __

[issue1294] Management of KeyboardInterrupt in cmd.py

New submission from BULOT: According to me, the Ctrl-C is not managed correctly in cmd.py. Ctrl-C generates a a KeyboardInterrupt exceptions, and only EOFError is managed. I propose to manage KeyboardInterrupt on line 130: print 'are you sure you want to exit? y/n'