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

Move configuration to TOML #158

Closed
CamDavidsonPilon opened this issue Jul 30, 2021 · 2 comments
Closed

Move configuration to TOML #158

CamDavidsonPilon opened this issue Jul 30, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@CamDavidsonPilon
Copy link
Member

CamDavidsonPilon commented Jul 30, 2021

Python seems to be adopting TOML more and more in its ecosystem 1 2, and TOML appears to be an improvement on INI, and simpler than YAML. Some considerations:

  1. Is there reliable backend/client JS TOML parser?
  2. TOML parser is not in the Python std library - but the parser is lightweight.
  3. The benefit of moving to TOML is not necessarily using their unique features, but avoiding error / ambiguity in users entering information.
  4. OTOH, there is some drama around which TOML library to use, and unmaintained libs.
@CamDavidsonPilon CamDavidsonPilon added the enhancement New feature or request label Jul 30, 2021
@CamDavidsonPilon
Copy link
Member Author

In Python 3.11 (unreleased as of today), there is a built in TOML library.

@CamDavidsonPilon
Copy link
Member Author

CamDavidsonPilon commented Apr 6, 2022

I don't think we should move to TOML

  • A TOML table must be populated in a single step; merging multiple TOML files is problematic
  • TOML re-introduces what human-friendly languages normally try to get rid of: a verbose syntax and the necessity of using quotes for strings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant