Minor suggestions for parallel module #81
Merged
Conversation
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
Updated most likely misinterpretation on part of caller.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Other than the minor verbiage changes (one unrelated to week11 that I noticed earlier), the main suggestion here is that I think we're introducing threads with async a little too soon, before the "regular" async stuff has been introduced. So I changed the existing
asyncpi.pyto not use threads, and moved your existing example toasyncpi_thread.py. If acceptable, feel free to change the wording to suit your needs.I had no idea about
InterpreterPoolExecutorand didn't realize thatif __name__ == "__main__"check is necessary for thespawnmethod, so this was very helpful!