Tina Müller (tinita)

The space is not redundant according to the current spec, and as you can see from the test results: https://matrix.yaml.info/details/Y2GN.html 11 parsers accept the colon, including relatively new libraries written...

> I'm confused why anyone is pushing back on this and saying that = should fail on parsing. = is not a special char in yaml. It definitely gives me...

The reason for that is, that a YAML document with only a plain scalar is considered "open-ended", and therefor needs an explicit document-end. So in this case the option is...

It has been explained in #379 that the current behaviour is necessary because of the YAML 1.1 spec.

> Even the example in the post doesn't have the end marks for the second value - why? because the important part in this example was the part after the...

I think the `open_ended` attribute would have to be changed from what it is doing right now in PyYAML. So, in YAML 1.2, the `...` is _always_ needed between two...

> I don't know if this is rare. The cases I meant are really rare. ``` key1: |+ some literal block scalar with trailing line breaks that should be preserved...

> PS: I'm curious about what @mikefarah and @ingydotnet think. Also @perlpunk, maybe you have an opinion on this? Just adding my 2 cents. I think the new option makes...

One problem is that this logic would break the functionality of merge keys: https://yaml.org/type/merge.html See `def flatten_mapping`. To fix this, we would need a seperate handling of the merge keys...

@marvingreenberg yeah, I think forbidding duplicate keys should be the default. Adding an option for disabling it might be nice. But merge key behaviour should stay the same. @ingydotnet is...