-
Notifications
You must be signed in to change notification settings - Fork 121
Issues: bw2/ConfigArgParse
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Multiline lists are not parsed in config files the way I'd expect
#299
opened Oct 31, 2024 by
agyoungs
ConfigArgParse is not handling the
--
seperator for positional arguments correctly
#298
opened Oct 31, 2024 by
agyoungs
Empty environment variable and empty yaml key behave differently
#296
opened Aug 22, 2024 by
rngadam
Abbreviated arguments don't show up in source_to_settings_dict
#286
opened Oct 11, 2023 by
wgreenberg
Are there config file includes (do config file attributes get parsed when they're in yaml)
#272
opened Apr 27, 2022 by
ridilculous
Positional config file arguments do not work when config file arg is not first
#265
opened Mar 4, 2022 by
benjamin-fenker
Config files render various errors in combination with default values
#260
opened Dec 16, 2021 by
ftrofin
[bug]Cannot override yaml settings on the command line when using the bool option with strtobool.
#259
opened Dec 10, 2021 by
MasanoriYamada
allow for choices to be empty in config file but not on command line
#257
opened Oct 29, 2021 by
mathisloevenich
Add option to disable commandline params for config file
#256
opened Oct 29, 2021 by
mathisloevenich
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.