Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Use YAML parser implementing YAML 1.2 rather than 1.1 #1885

Open
non-Jedi opened this issue Feb 5, 2017 · 1 comment
Open

Use YAML parser implementing YAML 1.2 rather than 1.1 #1885

non-Jedi opened this issue Feb 5, 2017 · 1 comment
Labels
A-Config Configuration, or the documentation thereof T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@non-Jedi
Copy link

non-Jedi commented Feb 5, 2017 •
edited
Loading

YAML 1.2 is a true superset of json. Using a parser that implemented 1.2 would allow configuration files written in json or yaml with no extra effort.

One possibility may be ruamel.yaml which is mentioned on yaml.org
@non-Jedi
Copy link
Author

non-Jedi commented Feb 5, 2017

There's a quick summary of the breaking changes between YAML 1.1 and 1.2 here. If the maintainers would be willing to make this change, I might take a stab at it myself.

@dklimpel dklimpel mentioned this issue May 9, 2022
Open
@reivilibre reivilibre added A-Config Configuration, or the documentation thereof T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. labels May 23, 2023
@matrixbot matrixbot mentioned this issue Dec 21, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
A-Config Configuration, or the documentation thereof T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@non-Jedi @reivilibre