This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | alexandre.vassalotti |
|---|---|
| Recipients | alexandre.vassalotti, draghuram, gvanrossum, stephbul |
| Date | 2007年12月04日.00:28:30 |
| SpamBayes Score | 0.0036426517 |
| Marked as misclassified | No |
| Message-id | <1196728111.34.0.828437092207.issue1294@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 command 'EOF'." For the KeyboardInterrupt issue, it thinks the exception should be handled by the application with a try-statement. For example, >>> import sys, cmd >>> c = cmd.Cmd() >>> try: ... c.cmdloop() ... except KeyboardInterrupt: ... print "\nGot keyboard interrupt. Exiting..." ... sys.exit(0) ... (Cmd) ^C Got keyboard interrupt. Exiting... I am closing and marking this bug as rejected. If you feel this is inappropriate, please request with an appropriate explanation to reopen it. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年12月04日 00:28:31 | alexandre.vassalotti | set | spambayes_score: 0.00364265 -> 0.0036426517 recipients: + alexandre.vassalotti, gvanrossum, draghuram, stephbul |
| 2007年12月04日 00:28:31 | alexandre.vassalotti | set | spambayes_score: 0.00364265 -> 0.00364265 messageid: <1196728111.34.0.828437092207.issue1294@psf.upfronthosting.co.za> |
| 2007年12月04日 00:28:31 | alexandre.vassalotti | link | issue1294 messages |
| 2007年12月04日 00:28:30 | alexandre.vassalotti | create | |