test_emitter.test_emitter_styles failing when using C extensions on python2 only

[dthkao]

I might be misunderstanding what is expected behavior, but at the very least there seems to be some inconsistency in test results described below.

When running test_emitter with python 2 using cython extension, the error I see is

AssertionError: (ScalarEvent(anchor=None, tag=u'tag:yaml.org,2002:str', implicit=(False, False), value=u'foo'), ScalarEvent(anchor=None, tag=u'tag:yaml.org,2002:str', implicit=(False, False), value=u'foo %YAML 1.1'))

Specifically, when I turn on verbose mode, for the test case (filename='third_party/py/yaml/tests/data/spec-07-09.canonical', flow_style=False, style=''), I see as the emitted output:

OUTPUT (filename='third_party/py/yaml/tests/data/spec-07-09.canonical', flow_style=False, style='')
%YAML 1.1
--- !!str foo
%YAML 1.1
--- !!str bar
%YAML 1.1
--- !!str baz

In comparison, for python 3 (with or without C extensions) and for python 2 without extensions I see this output with verbose on:

OUTPUT (filename='third_party/py/yaml/tests/data/spec-07-09.canonical', flow_style=False, style='')
%YAML 1.1
--- !!str 'foo'
%YAML 1.1
--- !!str 'bar'
%YAML 1.1
--- !!str 'baz'

So this really brings up 2 questions for me:

1. In the passing test cases, why isn't the emitted style "plain" (no quotes)?
2. What's different for py2 w/ extensions?

[perlpunk]

I can't say anything about the different behaviour of python 2 and 3 right now, but the error you see (getting foo %YAML 1.1 instead of just foo) stems from a bug in libyaml which will be fixed with the next release. See yaml/libyaml#122

[dthkao]

Thanks! I am curious why the behavior differs, as well as why the plain-style scalar events are emitted with quotes. Is this a special case of YAML 1.1?