Add BuildTree class #38
Merged
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
bnemanich
force-pushed
the
create_build_tree_class
branch
from
80f3ebc
to
963a289
Compare
bethune-bryant
previously requested changes
Sep 28, 2020
bethune-bryant
approved these changes
Sep 28, 2020
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.
This PR creates 2 new classes.
BuildCommand
Holds all of the information needed to perform a single run of build_feedstock. Provides two helpful methods:
feedstock_args: This will return a list of strings that can be passed to build_feedstock to perform a build.
name: This will print out a name for the command, combining the recipe name with the python versions and build_type.
BuildTree:
Container for a list of BuildCommands.
The constructor will clone all of the feedstocks specified in the provided environment files and create a list of BuildCommands using the dependency information found in the recipe's meta.yaml files.
Iterating over the BuildTree will ensure that all dependent packages appear before any packages relying on them.
Indexing into the BuildCommand will correlate to the indices provided in a BuildCommand's build_command_dependencies field.