complete implementation of (very) initial support for easyconfig format 2.0#810
complete implementation of (very) initial support for easyconfig format 2.0#810boegel merged 25 commits intoeasybuilders:developfrom
Conversation
…version operator parsing failure
…), start implementation of get_specs_for function
…True to allowed builtins used in Python header
…ment asdict function to obtain dict representation of EasyConfig instance
…ize toy build unit test module
There was a problem hiding this comment.
is the avoidance of templates on the 2 lines above intentional?
There was a problem hiding this comment.
@boegel can you use at least one template constant here; it should still work.
There was a problem hiding this comment.
OK, used constants for both of these.
There was a problem hiding this comment.
so, most of the PR is about adding yet another argument (specs) and just pass it along. all options that are passed through from main to easyconfig should be packed in eg a dict or another object. (for now it looks like check_osdeps and specs are the ones)
all current arguments can be left if they belong to the API, but should marked deprecated.
There was a problem hiding this comment.
at the very least update the docstring when adding new arguments
There was a problem hiding this comment.
reworked to only have build_options and build_specs class parameters, both dictionaries
|
@stdweird: I took care of all remarks, but I still need to make the |
There was a problem hiding this comment.
should this be the default instead of None? you can make the condition to log a simple ```if 'valid_module_classes' in build_option.
|
@boegel 2nd pass done, i made some remarks that i deleted again because the coffee hasn't kicked in yet.... |
|
@stdweird: second round of remarks covered, so good to go, and continue in future PRs? |
|
@boegel 2 tiny remarks, ready to merge |
|
Last tiny remarks resolved, merging in this beast. |
complete implementation of (very) initial support for easyconfig format 2.0
Building
gzipwith the includedgzip.ebworks, version and toolchain can be specified, default values are picked according to the[DEFAULT]section.Examples of usage: