- Notifications
You must be signed in to change notification settings - Fork1.4k
Correct exitcode of KeyboardInterrupt#4414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
vm/src/vm/mod.rs Outdated
| self.print_exception(exc); | ||
| #[cfg(windows)] | ||
| { | ||
| winapi::winnt::STATUS_CONTROL_C_EXIT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
maybe adding a feature related to winnt will be helpful
83bf3e8 to2444961Comparemoreal commentedJan 8, 2023
I tried to implement for targets (not unix) but there were some issues:
So this pull request became to implement only for unix now. Other pull request will resolve the problem in windows and wasm instead. |
2444961 to3f98f68Compare3f98f68 to16579aeCompare
youknowone left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thank you!
Uh oh!
There was an error while loading.Please reload this page.
This pull requests fixes exitcode of
KeyboardInterrupt. You can run the below code with CPython and RustPython(before/after). (in unix target os)Tasks
windowswasmRelated links