-
Notifications
You must be signed in to change notification settings - Fork 750
Rebased PR 450 (Py_Initialize without overriding signals) #724
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebased PR 450 (Py_Initialize without overriding signals) #724
Conversation
@filmor why is this failing CI? |
Something about |
Codecov Report
@@ Coverage Diff @@
## master #724 +/- ##
=========================================
Coverage ? 75.58%
=========================================
Files ? 60
Lines ? 5627
Branches ? 888
=========================================
Hits ? 4253
Misses ? 1060
Partials ? 314
Continue to review full report at Codecov.
|
168ec06
to
e2b8c25
Compare
@filmor, the only change in this code is optionally calling InitializeEx instead of Initialize. This code is often being touched by tests. The actual change here is really simple, the unit test is excessively complex. Could you consider merging this without a unittest testing CTRL+C explicitly? |
cabeec8
to
f9810f8
Compare
I think you are right. I'll merge the PR without the unit test using a merge commit, that way the test is at least present in the history. |
e38124a
to
3d6024d
Compare
@rmadsen-ks
What does this implement/fix? Explain your changes.
Avoiding overriding signals from the application so that CTRL-C might be handled.
Using Py_InitializeEx(0) (instead Py_Initialize) to avoid overriding signals.
Does this close any currently open issues?
#449 #450
Any other comments?
Just a rebased version of #450.
Checklist
Check all those that are applicable and complete.
AUTHORS
CHANGELOG