acquire a global lock to init the OpenSSL singleton locks #2336
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.
...then init the library since we really only want to do that once anyway
This approach was suggested in #2299. Of note, in a subinterpreter environment a "random" subinterpreter will register the static locks and engine. This means it will contain the Python callbacks for them. If the subinterpreter is subsequently destroyed, do the locks and random engine continue to function? If not, this solution will not work.
This should be considered WIP until we have a solid answer to the above.