-
Notifications
You must be signed in to change notification settings - Fork 188
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
Use disable_sigint instead of sigatomic_(begin|end) #686
Conversation
So it seems that just switching to Before 6ca05f4
After 6ca05f4
|
What is the relationship of this PR to #574? |
The first commit c030fdd in this PR is included in #574 but #574 comes with more "destructive" changes. This is a safe subset of #574. The second commit 6ca05f4 is a fix for the possible performance regression ( |
Since `Py_CompileString` is unlikely to call Julia callback, there is no need to put it in `disable_sigint`. `@pycheckn` for `PyEval_EvalCode` is in `disable_sigint` because `PyErr_NormalizeException` may call the constructor of the exception class which may invoke Julia callbacks. This change may not be necessary but it seems to help Julia compiler inlining `ccall`.
AppVeyor failures are the same as #687. Merging... I'm not using squash since each commit has distinct information. |
close #684