You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't exactly a bug itself, but can contribute to bugs, including one that stumped @jedwards4b and me for a while this week: The order of the command-line arguments to the buildlib script, when called as a subprocess, differs for libraries
One implication of this is that the parse_input command in buildlib.py cannot be used for libraries.
Changing the argument order for components would be a pain (requiring coordinated changes in a bunch of repositories). But I wonder if it would be feasible to change the argument order for libraries to match that of components?
Even better would be changing these positional arguments to named arguments – for both libraries and components – but I can't think of a backwards compatible way to do that (so again, it would require coordinated updates in a bunch of repositories).
The text was updated successfully, but these errors were encountered:
This isn't exactly a bug itself, but can contribute to bugs, including one that stumped @jedwards4b and me for a while this week: The order of the command-line arguments to the buildlib script, when called as a subprocess, differs for libraries
cime/scripts/lib/CIME/build.py
Lines 462 to 463 in 4312d85
vs components
cime/scripts/lib/CIME/build.py
Lines 514 to 515 in 4312d85
One implication of this is that the
parse_input
command inbuildlib.py
cannot be used for libraries.Changing the argument order for components would be a pain (requiring coordinated changes in a bunch of repositories). But I wonder if it would be feasible to change the argument order for libraries to match that of components?
Even better would be changing these positional arguments to named arguments – for both libraries and components – but I can't think of a backwards compatible way to do that (so again, it would require coordinated updates in a bunch of repositories).
The text was updated successfully, but these errors were encountered: