Skip to content

Conditionally use valid_signals.#880

Merged
clalancette merged 1 commit intohumblefrom
clalancette/humble-check-for-valid-signals
Feb 6, 2024
Merged

Conditionally use valid_signals.#880
clalancette merged 1 commit intohumblefrom
clalancette/humble-check-for-valid-signals

Conversation

@clalancette
Copy link
Copy Markdown
Contributor

On Python 3.6 (in RHEL-8), signal.valid_signals()
does not exist. Only use it if it exists.

This should fix #879 . Note that we only need this fix on Humble, since we don't have to worry about Python 3.6 on Iron and later.

On Python 3.6 (in RHEL-8), signal.valid_signals()
does not exist.  Only use it if it exists.

Signed-off-by: Chris Lalancette <clalancette@gmail.com>
Copy link
Copy Markdown
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with green CI

@clalancette
Copy link
Copy Markdown
Contributor Author

clalancette commented Feb 2, 2024

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status
  • RHEL Build Status

@clalancette clalancette merged commit 8df36c4 into humble Feb 6, 2024
@delete-merged-branch delete-merged-branch bot deleted the clalancette/humble-check-for-valid-signals branch February 6, 2024 13:03
@cottsay cottsay linked an issue Feb 16, 2024 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incompatibility of humble with python3.6: signals.valid_signals()

2 participants