Comments (1)
Hey there @nacitar , sorry for replying earlier.
This is a cute, crunchy little bug. I really like those.
For anyone that wants to help out, this is what I'm thinking:
- This is most likely due to the help formatter used by default (the default value of the
formatter_class
argument ofsimple_parsing.ArgumentParser
): the SimpleHelpFormatter.
What I suggest trying:
- Try using the original
argparse.ArgumentDefaultsHelpFormatter
. Check if the problem persists.- If the problem doesn't show up, then the bug is inside our help formatter subclass.
- If the problem persists, then try using no help formatter at all (passing None as
formatter_class
I think).- If the problem is fixed, then the bug is probably happening inside the help formatter from argparse.
- If the problem still persists, then it must be something in the way we create the value of the
help
argument toadd_arguments
of argparse, probably in theFieldWrapper
in simple_parsing.
from simpleparsing.
Related Issues (20)
- Make `simple-parsing` faster HOT 4
- Clean up display of help message HOT 2
- Unintuitive inconsistent behavior for `Optional` between builtin classes and `dataclass`es
- Export args to a schema file so that YAML language servers can understand config files HOT 3
- adding yaml config interpolation HOT 5
- Bug: unexpected keyword argument not detected when nesting dataclasses HOT 3
- Is it possible to model a list of configs using inheritance? HOT 1
- Union of singular type with list of types not behaving as expected. HOT 6
- scientific notation in dict values doesn't get converted to float HOT 2
- Allow only a single cli argument for multiple different dataclasses. HOT 2
- Bug with subgroups and None HOT 1
- Excessive logging at the INFO level HOT 1
- Parse list object from both "--a_list 1 2 3" and from "--a_list '1 2 3' " HOT 4
- Subparsers overwrite kwargs of original parser HOT 1
- Postprocessing wraps defaults during postprocessing HOT 2
- Reaching `ConflictResolutionError` on too big/nested and shared configs with more than 50 parameters. HOT 3
- decoding_fn never gets called HOT 2
- Dataclass arguments added after `parse_known_args` call don't get added to help HOT 2
- `Type | None` or `Optional[Type]` don't work when default value is `None`
- `Type | None` or `Optional[Type]` don't work when default value is `None`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from simpleparsing.