SimpleParsing
SimpleParsing copied to clipboard
lebrice
Simple, Elegant, Typed Argument Parsing with argparse
**Is your feature request related to a problem? Please describe.** I would like to have a set of parameters that are optional, but if you give one of the set,...
**Describe the bug** SimpleParsing doesn't currently account for conflict in option strings between "regular" arguments (added through `parser.add_argument("--foo", default=123)` and through `parser.add_argument(DataclassWithFooField, dest="bar")`. **To Reproduce** (modified example from #46 )...
**Is your feature request related to a problem? Please describe.** I need to parse nested tuples, as often occur in parameterization -- ie a tuple of (a tuple of names,...
**Describe the bug** Hi, thanks for the amazing work! I am honestly not sure, whether this should be classified as a bug or not, because it is a default behaviour...
**Describe the bug** OK so this one is tricky and very specific, and shouldn't impact anyone really. When we're trying to parse multiple lists using the same attribute (no prefixing,...
Currently, `simple_parsing` force to add comments along the attributes they are defined It would be nice if it was also supporting the google docstring style `Attributes` field: https://google.github.io/styleguide/pyguide.html#384-classes ```python @dataclass...
Fixes #163 TODOs: - [ ] Figure out how prominently to show the `parse` api in the readme. - [ ] Add tests for the `parse` api (a LOT of...
I thing that the code to parse simple, most basic use case is a little bit too complicated: ```python from dataclasses import dataclass from simple_parsing import ArgumentParser @dataclass class HParams:...
Allow to suppress the prefix defined for a field if used through an alias, for extra-short aliases for often-used command line switches.
**Describe the bug** Not sure whether it's a bug, or it's expected: After specifying the default config in a `subgroups`, changing the inner attributes of the default configuration requires prior...
