-
Notifications
You must be signed in to change notification settings - Fork 24
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
UW-209 #129
Comments
Test comparisons are as follows: INI vs F90 YAML vs INI YAML vs F90 F90 vs INI F90 vs YAML The direct conversion reads from the base object correctly, but once it reads from a dictionary object, there are issues with all dump calls. Primarily, its 'detecting' the dictionary as an OrderedDictionary nested within a standard dictionary, but ConfigParser and YAML don't support ordered dictionaries. There is a workaround updated parser called ConfigObj, but it doesn't allow formats outside of standard INI. It would take some extra steps to get the formatting and string stream into it. YAML I haven't found an answer for yet, could be a newer fork that can handle it. The F90 parser just treats it as an unordered dictionary and scrambles the keys. |
I think there are 2 main things going on here...
|
Solved by #131 |
Description
https://jira-epic.woc.noaa.gov/browse/UW-209
Requirements
Test that the assumptions that the polymorphism built into the Config subclasses for YAML, namelists and INI files is sufficient to transform to another subclass. May require making the input file path optional in the 'init' methods of each.
Acceptance Criteria (Definition of Done)
One additional test in test_config.py must test all transform combinations and complete successfully
The text was updated successfully, but these errors were encountered: