Tina Müller (tinita)

Unfortunately there is some other code that needs to be changed before this. If you take this code: ``` import sys import yaml output = yaml.emit(yaml.parse(sys.stdin.read())) sys.stdout.write(output) ``` and feed...

Thanks! I checked libyaml and I think it's ok to do that without changing the macro. Made a PR: https://github.com/yaml/libyaml/pull/170

Thanks! My suggestion is we do a libyaml release soon, and then we can use the new libyaml here, so the tests will pass.

See Ingy's comment here: https://github.com/yaml/libyaml/pull/170#issuecomment-605720525 I have to revert my PR for libyaml. This PR has to be postponed until it's clear what should be done. Sorry :-/

Travis CI is currently failing because of the libyaml tests. Working on that in #404

@artificial-aidan I fixed the libyaml tests with this: https://github.com/yaml/libyaml/commit/a718a893542e7cf9ab8862d2ef8c43d33644cc8d Retriggered the tests

Good question - I think it's an oversight that happened when we generated the test and used a libyaml based parser, which can't parse this input...

That's an oversight, thanks. We are now generating the event list automatically with the reference parser, but only in the case of valid test cases. For invalid cases the process...

I think for the current format we don't have a tool right now. We used a tool when the test files were still using the tml format. Maybe @ingydotnet knows...

No. ;-) but have a look at https://github.com/perlpunk/yaml-test-schema which has a pretty complete list of tests regarding resolving booleans, numbers etc. the test suite here concentrates on parsing / syntax.