JSON6 | pyspnego | |
---|---|---|
1 | 1 | |
231 | 50 | |
- | - | |
10.0 | 6.2 | |
over 2 years ago | 2 months ago | |
JavaScript | Python | |
GNU General Public License v3.0 or later | MIT License |
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.
JSON6
-
TOML: Tom's Obvious Minimal Language
I pretty like the idea of a superset of JSON taht supports (1) comments, (2) trailing commas, (3) unquoted properties, (4) optional {} for the root object, (5) multi-line strings, (6) number separator.
JSON6 proposal [1] supports all of this, except (4). Unfortunately it also supports more and make the spec a bit too complex for my taste (JSON has a compact spec; any extension should honor this). Same issue with JSON5 proposal [2].
EKON [3] is certainly the best candidate. However, it doesn't get any traction.
[1] https://github.com/d3x0r/JSON6
pyspnego
-
TOML: Tom's Obvious Minimal Language
Can you share an actual example where you need to specify requirements twice. With pyproject.toml I know of 3 ways requirements are specified and they are all used by different things:
1. Build requirements - requirements needed to build your package from an sdist
2. Runtime requirements - requirements your library needs at runtime
3. Extra requirements - optional runtime requirements
For example my library pyspnego https://github.com/jborean93/pyspnego/blob/main/pyproject.to... has all 3:
1. Cython for Win32 needed to build the sdist and setuptools as the general build system - https://github.com/jborean93/pyspnego/blob/c3db058b636fc102f...
2. cryptography as a runtime dependency - https://github.com/jborean93/pyspnego/blob/c3db058b636fc102f...
3. optional extras kerberos and yaml - https://github.com/jborean93/pyspnego/blob/c3db058b636fc102f...
Granted the toml format and what is used in pyproject.toml has it's warts but I'm curious what your joke and clown_fiesta examples are actually from as from where I am standing each section currently serve different purposes.
What are some alternatives?
gura - Gura configuration language
ekon - A JSON alternative for sane people. Combination of simplicity & power. Check it out!
config - configuration library for JVM languages using HOCON files
pytoml - A TOML-0.4.0 parser/writer for Python.
knot8 - define and manipulate "knobs" in K8s manifests
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
toml - Tom's Obvious, Minimal Language
rust-playground - The Rust Playground