Make a few more safety improvements #16
Merged
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.
This is mainly just about converting the RwLock to a Mutex to be absolutely sure there can never be one
ensure_python_event_loopcreating a new loop while another is about to write its own created loop. Rather than allowing and writes to interleave we just fully lock it down so any access has to wait until the full logic is complete. Because we never actually read this outside of construction, we don't really need to care about the perf difference between a Mutex and a RwLock.