Flatten the implementation of the pipeline() decorator. #43
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
It seems easier to follow in a single function rather than being spread out in multiple helpers. (It also makes the signature of `pipeline()` explicit without having to duplicate it.)
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.
It seems easier to follow in a single function rather than being spread out in multiple helpers. (It also makes the signature of
pipeline()explicit without having to duplicate it.)Note, by the way, that the
func(*ancestors, *args, **kwargs)branch occurs for two opposite values ofall_pipedepending on whetheris_classis true or false. This looks a bit strange to me, but it's hard for me to say whether it's a bug or not.