Skip to content
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

config nestedness, yaml and toml #110

Open
rhizoome opened this issue May 7, 2024 · 0 comments
Open

config nestedness, yaml and toml #110

rhizoome opened this issue May 7, 2024 · 0 comments

Comments

@rhizoome
Copy link

rhizoome commented May 7, 2024

I switched to toml, because I had an issue with the nestedness of the config and because I wanted to get rid of C-extensions in pyaptly. I did not find an acceptable pure python yaml parser.

While the converter from yaml to toml did an ok job for the configs we use in our tests. It made a complete mess on the existing productions configs. Currently I think, there is a nice config that is correct toml, but the converter is just messing it up.

What I am going to do:

  • Try to fix the converter

Questions:

  • Is manual cleanup acceptable if we can't fix the converter?
  • Do we really need to get rid of C-extensions?
  • Should we just support toml and yaml?
  • Forget toml completely?
  • Should the nestedness be fixed in the data-structure?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant