Add explicit Numpy import to workaround GIL deadlock with asyncio. #155
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.
See #154.
In certain situations (including when using asyncio), Pedalboard's C++ code will implicitly and lazily import NumPy via its Pybind11 bindings. This lazy import can sometimes (!) cause a deadlock on the GIL if multiple threads are attempting it simultaneously. To work around this, we preload Numpy into the current Python process so that Pybind11's lazy import is effectively a no-op.
No tests included here: the buggy behaviour occurs when
numpy
isn't loaded into the running Python process, which is very hard to simulate in test without running a subprocess and writing a very elaborate (and likely brittle) test.