-
Notifications
You must be signed in to change notification settings - Fork 4
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
Switching to YAML for config #128
Comments
Leaving aside the question of attributes, YAML seems like an easy choice.
Example:
A few issues:
|
Also: pathlib.Path (Python 3.4) for all Paths class operations |
Note: using os.access on pathlike object (e.g. pahlib's Path class) requires 3.6 |
Still to do:
|
We can now save and read state.yaml including converting time_structs and pathlib.Paths back and forth. Still to do in addition to those mentioned above:
|
brokkr
changed the title
Switching to JSON/YAML for config
Switching to YAML for config
Jul 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe either JSON or YAML would allow for significant code simpification (there's a lot of lines just parsing the XML). And I don't believe we really depend on the things that XML brings to the table (namespaces etc.)?
Advantages of JSON: Built-in (one less dependency), fast
Advantages of YAML: Easy to read, supplanting pickle?
Really depends on how well either one deals with the heavily nested structure of say, a subscription with filters and metadata and renames... Also how would attributes translate?
The text was updated successfully, but these errors were encountered: