- Notifications
You must be signed in to change notification settings - Fork750
Minimal Py_IntializeEx change#777
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
codecovbot commentedNov 15, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## master #777 +/- ##==========================================- Coverage 77.04% 63.6% -13.45%========================================== Files 63 1 -62 Lines 5786 283 -5503 Branches 911 0 -911 ==========================================- Hits 4458 180 -4278+ Misses 1024 103 -921+ Partials 304 0 -304
Continue to review full report at Codecov.
|
43c56bb
to62634f9
Compare@filmor why did you switch both x86 & x64 to AnyCPU? |
Argh, sorry, I wanted to exclude this part from the branch :/ I'll revert that particular change. |
@filmor py27 got stuck in appveyor for master branch. I restarted the build. |
What does this implement/fix? Explain your changes.
Minimal version of#724, allows the user to select whether an embedded Python should configure signal handlers or not, defaulting to "false" (which is different from what we had before as a straight call to
Py_Initialize
will configure signal handlers).Does this close any currently open issues?
Fixes#449.
Any other comments?
We should follow up on#724 to get a unit test working for this, but this can wait until after 2.4.0.