Skip to content
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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix #2 signal issue on py34 #3

Merged
merged 4 commits into from
Mar 13, 2015
Merged

Fix #2 signal issue on py34 #3

merged 4 commits into from
Mar 13, 2015

Conversation

swistakm
Copy link
Collaborator

Fix #2 issue on python3.4 caused by OSError exception not catched when trying to bind SIGSTOP signal

@coveralls
Copy link

Coverage Status

Coverage increased (+19.16%) to 78.92% when pulling d9e3c3d on swistakm:fix/ianitor-signal-issue-on-py34 into dc4698f on ClearcodeHQ:master.

swistakm added a commit that referenced this pull request Mar 13, 2015
@swistakm
Merge pull request #3 from swistakm/fix/ianitor-signal-issue-on-py34
6a2c1a8 
Fix #2 signal issue on py34
@swistakm swistakm merged commit 6a2c1a8 into ClearcodeHQ:master Mar 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

ianitor OSError: [Errno 22] Invalid argument
2 participants
@swistakm @coveralls