Conversation
fuzzyman on Feb 27, 2010")
Conflicts: easybuild/framework/easyconfig/easyconfig.py setup.py test/framework/easyconfig.py test/framework/suite.py
…easyconfigs format v1.0, to allow for lists specified on a separate line
fix merge with develop, fix framework/easyconfigs unit tests on top of this
There was a problem hiding this comment.
Can you elaborate a bit on this? Do you want to allow for specifying as which version (1.0, 2.0) an easyconfig file should be parsed?
There was a problem hiding this comment.
yes, eg via commandline option to override whatever is set in the easyconfig. but i'm not sure if there is a valid use case. ignire or open a ticket.
There was a problem hiding this comment.
We can make the code support it regardless of having a command line option for it, in any case. I'll try and tackle this.
There was a problem hiding this comment.
making these lists makes more sense imho, although that does make these "constants" mutable
tuples are not for listing things that are of the same type, they have a certain (mathematical) semantic
…idate_and_filter_by_toolchain() and (sort of) complete the implementation of it (recurse); also: make unit tests happy
…s 'main' for sections
|
@stdweird: I'm done restepping through this beast, I fixed most of the remarks I made in stdweird#22. Just check back here after you review and merge that one, I think there might be a couple of (minor) open questions in here. After my PR is merged into your repo, I'm very keen on merging this is as is. All the unit tests pass, so this shouldn't break easyconfig format 1.0 in any way. Let me know if you're OK with this, I'll then recheck any open comments here and simply add |
|
Hmm, hold on, I'll need to fix the failure with Python 2.6 and Python 2.4 first, see https://jenkins1.ugent.be/view/EasyBuild%20(boegel)/: |
note (20130924): not yet finished, this is currently a placeholder for more work on this