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 package came up in a conversation about how to handle some command-line parameters that will potentially be in-common across several of the case_utils commands:
One example is the "Local UUID" opt-in mechanism, that generates consistent UUID5s with some dependencies on an environment variable.
Another example is a coming incorporation of this script's UUIDv5 IRI scheme for uco-types:Hash nodes - which I think should be opt-in, but the place where that opt-in check would be made could potentially be deep in a shared library.
If we find a demonstration of multiple use cases, we might want to consider ConfigArgParse or something similar if it offers sufficient advantages over copying and pasting .add_argument("--...") lines between scripts.
The text was updated successfully, but these errors were encountered:
This package came up in a conversation about how to handle some command-line parameters that will potentially be in-common across several of the
case_utils
commands:https://pypi.org/project/ConfigArgParse/
One example is the "Local UUID" opt-in mechanism, that generates consistent UUID5s with some dependencies on an environment variable.
Another example is a coming incorporation of this script's UUIDv5 IRI scheme for
uco-types:Hash
nodes - which I think should be opt-in, but the place where that opt-in check would be made could potentially be deep in a shared library.If we find a demonstration of multiple use cases, we might want to consider
ConfigArgParse
or something similar if it offers sufficient advantages over copying and pasting.add_argument("--...")
lines between scripts.The text was updated successfully, but these errors were encountered: