pycall 1.5.1 => pycall 1.5.2 - #60330
Merged
Merged
Conversation
Contributor
Author
|
Merging now because this particular bug makes me nervous and I'd like it into the prod servers asap. It was an oversight on my part that we shipped with pycall 1.5.1, I had been doing all my testing on 1.5.2 but screwed up a merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've been reading a lot of pycall source code, and
pycall 1.5.2has a fix I'd like to pull in, without it there's a potential segfault on ruby exit.The change I want in particular is: red-data-tools/pycall.rb@9a40e6b