Tina Müller (tinita)

It's an issue regarding YAML 1.1 and 1.2. Just adding quoting here and there doesn't fix the general problem. There must be real support for YAML 1.2. See https://perlpunk.github.io/yaml-test-schema/schemas.html But...

Btw, I just tested ruamel.yaml (0.16.10), and it resolved the following items as numbers/timestamps/etc., although that doesn't match the spec. They should *all* be loaded as strings when using the...

> You can use ruamel.yaml instead Except that ruamel.yaml is wrong in some other cases (tested with 0.17.20) as I wrote here: https://github.com/yaml/pyyaml/issues/98#issuecomment-630756369

Option 2 I would recommend to use a submodule with a certain data release tag. I believe this use case is something submodules were invented for. Where do you see...

my point was to use a data release tag. example: https://github.com/yaml/yaml-test-suite/releases/tag/data-2022-01-17 the data exports have all files readily available. no need for `make data-update`. it's documented in the readme. the...

Some background on this: There is a discussion that repeated anchors should be forbidden in the next version of YAML (AFAIK mainly because it makes roundtripping with keeping anchor names...

@yamlCase actually the public process of RFCs has just started these days. This is the related RFC: https://github.com/yaml/yaml-spec/pull/65 Note that the Pull request for the RFC itself is not where...

rebased and retargeted to release/6.0

We had a meeting and discussed this. I added an option `reuse_anchors` that defaults to `False`, like requested.

It is considered for the next release 6.1, I believe