yamlloader
pyyaml
| yamlloader | pyyaml | |
|---|---|---|
| 1 | 17 | |
| 33 | 2,441 | |
| - | 1.3% | |
| 0.0 | 3.5 | |
| 6 months ago | 2 days ago | |
| Python | Python | |
| MIT License | 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.
yamlloader
pyyaml
-
Troubleshoot dependencies in Pipfile/pipenv
Then I went to Uncle Google for cython and got this issue from last year: https://github.com/yaml/pyyaml/issues/724 Good news - it's closed!
-
Cython 3.0 Released
PyYAML knew about the breakage since january 2022[0], and nothing really happened. After a year and a half with lots of alphas and betas, I don't think there is much cython could do, short of fixing PyYAML themselves.
[0]: https://github.com/yaml/pyyaml/issues/601
- Cython v3 release breaking PyYAML install well used in Python ecosystem
- Cython and pyyaml is breaking many builds
- I'm needing a hand, I do not understand some (seemingly) simple Python stuff.
-
is there any difference between using string.format() or an fstring?
They did finally change the default, in PyYAML 6, after many many bugs pointing out that their previous approach is broken (including one by yours truly), so the default is now safe.
-
Using Rust to not have to touch Yaml in k8s land
Note some parsers, most notably pyyaml are still at yaml 1.1, because 13 years is just not enough time to update it.
-
JSON is not a YAML subset
That part of the YAML 1.2 spec is in conflict with reality, though. The base of YAML 1.1 documents is large enough that a backwards-incompatible change to default behavior is for practical purposes impossible.
YAML 1.1 was released in 2005, and 1.2 in 2009 -- only four years later. But here we are, in 2022, and YAML 1.1 is still the default (in many cases, only) version supported. That's why the "Norway problem" persists -- it's not possible for the parser to know whether an un-versioned YAML document containing "a: no" should parse the same as {"a": false} or {"a": "no"}.
Python (PyYAML) doesn't support 1.2 yet: https://github.com/yaml/pyyaml/issues/116
Ruby (Psych) ditto -- I can't even find a tracking issue to enable it.
Go (go-yaml) is a mixture of YAML 1.1 and 1.2, depending on the author's preferences.
Also, as a rough guideline, you can't have a backwards-incompatible revision of a versioned spec declare that it's the new default version, because that breaks all existing users.
-
I accidentally used YAML.parse instead of JSON.parse, and it worked?
Many parsers either default to YAML pre-1.2 or do not even expose a YAML 1.2 option. PyYAML has no 1.2 option, for example. So unless Ansible is using something other than PyYAML...
Relevant (open) PR: https://github.com/yaml/pyyaml/pull/555
- AttributeError: '_io.TextIOWrapper' object has no attribute 'items'
What are some alternatives?
confuse - painless YAML config files for Python
strictyaml - Type-safe YAML parser and validator.
yamllint - A linter for YAML files.
jsonnet - Jsonnet - The data templating language
marshmallow - A lightweight library for converting complex objects to and from simple Python datatypes.
python-strict-yaml-parsing - Examples of strict yaml parsing in python
python-frontmatter - Parse and manage posts with YAML (or other) frontmatter
kubernetes - Production-Grade Container Scheduling and Management
dhall-lang - Maintainable configuration files
yaml-spec - YAML Specification
toml.io - Source Code for toml.io
awesome-json-next - A Collection of What's Next for Awesome JSON (JavaScript Object Notation) for Structured (Meta) Data in Text - JSON5, HJSON, HanSON, TJSON, SON, CSON, USON, JSONX/JSON11 & Many More