Implement signal constants on POSIX platforms#1945
Merged
BCSharp merged 9 commits intoIronLanguages:mainfrom Apr 14, 2025
Merged
Implement signal constants on POSIX platforms#1945BCSharp merged 9 commits intoIronLanguages:mainfrom
BCSharp merged 9 commits intoIronLanguages:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What has changed:
signalare changed to reflect the actual values on a given platform (previously the values were always Windows-specific).test_signalfrom the IronPython test suite is modified to pass with CPython on all OS platforms supported by IronPython.signalis modified to pass the modifiedtest_signal. This in practice means primarily changes to error handling.What has not changed:
SIGINTandSIGBREAK, and onlySIGINTon Unix; no new signals are being handled yet).signal.