sort kwargs in lh.move_resource #359
Open
+46
−9
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
both
LiquidHandlerBackend.{pick_up,drop}_resourcetake can kwargs. These are often different (eg channels for core-gripper pickup in STAR - not an argument to drop). In the past, lh would send the full set of backend_kwargs to both mehods which caused an error for some backend methods if only one of {pick_up,drop} accepted a kwargs. This PR fixes that by removing kwargs not accepted by the backend method before passing them.One complication is truly unnecessary params are removed in both cases, without an error to the user. I might add a special error case in lh.move_resource, but this isn't the prettiest. tbd
ref: i split move_resource as a backend method into separate methods in #328