| tomli | json5 | |
|---|---|---|
| 5 | 94 | |
| 439 | 6,301 | |
| - | 0.9% | |
| 3.0 | 0.0 | |
| 6 days ago | 5 months ago | |
| Python | JavaScript | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tomli
-
What Is Wrong with TOML?
But the whitespace handling involved is an extra complication, at least the provided example fails to be parsed by `tomli`, which is following the currently release TOML spec: https://github.com/hukkin/tomli/issues/199
-
ConfigParser potential inconsistencies
ini files aren't standardized, the syntax is really "whatever the parser implements". For new projects I recommend using toml instead. It's ini-like, but standardized. Python 3.11 even comes with a builtin parser tomllib (earlier python versions can use tomli, which is what tomllib is based on).
-
Python 3.11 will now have tomllib - Support for Parsing TOML in the Standard Library
tomllib is primary the library tomli: https://github.com/hukkin/tomli
-
Upcoming Python Features Brought to You by Python Enhancement Proposals
TOML as a format is by default used by many Python tools, including build tools. This creates a bootstrapping problem for them. Additionally, many popular tools such as flake8 don't include TOML support citing its lack of support in standard library. This PEP proposes to add TOML support to standard library based on tomli which is already used by packages such as pip or pytest.
-
Comparison of Python TOML parser libraries
tomli Relatively fast read-only parsing. Companion library tomli-w for writing.
json5
- JSON5 – JSON for Humans
- Why the fuck are we templating YAML? (2019)
-
I pre-released my project "json-responder" written in Rust
JSON5 support
-
topoconfig: enhancing config declarations with graphs
Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.
-
That's a Lot of YAML
I think JSON5 is fairly close to this: https://json5.org
I reckon the only thing it's missing to be truly accessible to non-techies is that string values still need to be quoted, i.e. you can't have:
key: this is my value
(I'm definitely not saying it would be a good idea to allow quotes to be dropped, just that that's the only potential stumbling block I see for non-techies.)
-
XML is better than YAML
I believe that's JSON5.
https://github.com/json5/json5
It's my preferred configuration file format, it fixes all the problems I have with JSON (trailing commas, comments) without turning it into a mess full of gotchas like YAML.
- Fx – Terminal JSON Viewer
- What Is Wrong with TOML?
-
🚀 'GET' API in API Maker
JSON 5 support
-
TySON: a native go library that lets you use TypeScript as an embedded configuration language without depending on Node or V8
I would like to see mention of JSON5 which is 11 years its elder. For comments in JSON, JSON5 is a good starting point.
What are some alternatives?
toml - Tom's Obvious, Minimal Language
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
tomlkit - Style-preserving TOML library for Python
hjson-js - Hjson for JavaScript
rtoml - A fast TOML library for python implemented in rust.
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
pytoml - A TOML-0.4.0 parser/writer for Python.
toml - Python lib for TOML
jsonnet - Jsonnet - The data templating language
tomlplusplus - Header-only TOML config file parser and serializer for C++17.
sublime-hjson - Hjson support for Sublime Text