ParmParse: pretty_print_table
#417
Conversation
Print to python output.
|
@WeiqunZhang @atmyers it would also be nice to implement a |
|
The values in PP_Entry are strings. A value of say |
|
Yep, I wouldn't know if there is a sensible order (hierarchy) to cast them. Could we simply store a type hint as well? Whenever a value gets added in the first place we know the type, don't we? Update: ah no, not if we get it from CLI or a text file of course 😅 But for anything programmatically added (i.e., C++ & Python added) we could actually store a hint with. |
## Summary Today, we use the `ParmParse` object not only anymore to read text-based key-value pairs from input files and CLI options, but additionally and sometimes exclusively populate it heavily from the C++ and Python APIs directly. This proposes a concept to store the type of the latest `add` with each entry, which can help to expose `ParmParse` options, e.g., when exporting them to Python dictionaries and other file formats (YAML, TOML, JSON, XML, etc.). When a typehint is found, we can cast to the correct type automatically for the value, instead of returning a string. ## Additional background AMReX-Codes/pyamrex#417 (comment) ## Checklist The proposed changes: - [ ] fix a bug or incorrect behavior in AMReX - [x] add new capabilities to AMReX - [ ] changes answers in the test suite to more than roundoff level - [ ] are likely to significantly affect the results of downstream AMReX users - [ ] include documentation in the code and/or rst files, if appropriate
Print to python output.