![]() ![]() My patch adds very sensible default behaviour when Ctrl-C or Ctrl-DĪre entered. Inappropriate, please request with an appropriate explanation to reopen it. I am closing and marking this bug as rejected. The command 'EOF'." For the KeyboardInterrupt issue, it thinks theĮxception should be handled by the application with a try-statement. The moduleĭocumentation states clearly that "End of file on input is processed as However, I believe the current behavior of cmd.py is correct. I recommend you find someone to help you come up withĪuthor: Alexandre Vassalotti (alexandre.vassalotti) *įirst, I would like to say thank you both for spending your time trying I don't think this is the right thing to do. It is only a ctrl-C management only, not a ctrl-D. Well, I made it with a diff -ruN, it works fine on my ubuntu. Patch is accepted, a doc change would be required in addition to theĬhange in doc string. Both of these can be overridden, if required. It terminates the session on CTRL-D and it just I am attaching a patch that changes the behaviour to a more typical one I tested cmd.py on Linux and two things (including the one reported byġ) CTRL-D produces a message "*** Unknown syntax: EOF".Ģ) CTRL-C produces a KeyboardInterrupt exception and the session terminates. I recommend you find someone to help you come up with Would you mind submitting a patch instead of a whole new file? Print 'are you sure you want to exit? y/n' I propose to manage KeyboardInterrupt on line 130: Generates a a KeyboardInterrupt exceptions, and only EOFError is FilesĪccording to me, the Ctrl-C is not managed correctly in cmd.py. Philip.Zerull, alexandre.vassalotti, draghuram, gvanrossum, isandler, ngie, stephbulĬreated on 12:51 by stephbul, last changed 14:56 by admin. ![]() Management of KeyboardInterrupt in cmd.py
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |