Remove return_result
argument from DDPSpawnPlugin.spawn()
#10867
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.
What does this PR do?
Part of #10034, #10059.
The argument
DDPSpawnPlugin.spawn(..., return_result=True|False)
was added in #10162 with the request from reviewer(s) that it remains configurable whether to create a mp queue or not. This becomes obsolete with #10034 and can be removed.Does your PR introduce any breaking changes? If yes, please list them.
Yes, anyone using the spawn() method on the plugin will not be able to pass the argument False anymore.
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
I made sure I had fun coding 🙃
Part of #1 (it's a lie, this is just here to avoid noisy GitHub bot)
cc @tchaton @justusschock @awaelchli @Borda @kaushikb11