PyYAML: Ticket Queryhttp://pyyaml.org/query?status=!closed&priority=high&desc=1&order=priority
YAML for Pythonen-USPyYAML/static/pyyaml.pnghttp://pyyaml.org/query?status=!closed&priority=high&desc=1&order=priority
Trac 0.12.2http://pyyaml.org/ticket/1
http://pyyaml.org/ticket/1#1: Can't make SVN checkout...Wed, 15 Mar 2006 09:18:31 GMTanonymous<p>
I use the SVN URL <a class="ext-link" href="http://svn.pyyaml.org/pyyaml/trunk"><span class="icon"> </span>http://svn.pyyaml.org/pyyaml/trunk</a> (from the Wikipage <a href="http://pyyaml.org/wiki/PyYAML">http://pyyaml.org/wiki/PyYAML</a> )
</p>
<p>
But i can't export or checkout: PROPFIND Error, 403 Forbidden ;(
</p>
Resultshttp://pyyaml.org/ticket/1#changeloghttp://pyyaml.org/ticket/128
http://pyyaml.org/ticket/128#128: libyaml should detect duplicate keys and report an error.Tue, 02 Jun 2009 23:00:04 GMTanonymous<p>
In the 1.1 spec I believe this is considered an error; currently libyaml silently accepts duplicate keys.
</p>
Resultshttp://pyyaml.org/ticket/128#changeloghttp://pyyaml.org/ticket/196
http://pyyaml.org/ticket/196#196: Uneccessry use of explict non-specific tagsThu, 28 Jul 2011 16:05:49 GMTanonymous<p>
I recently noticed that libyaml is putting an explicit non-specific tag on every string that has characters that need to be escaped. For example:
</p>
<ul><li>"This is an 'example'."
</li></ul><p>
Comes back as:
</p>
<ul><li>! 'This is an <em>example</em>.'
</li></ul><p>
The <tt>!</tt> sign is gratuitous, as it is completely unnecessary. For documents that humans may need to read it greatly detracts from readability, so it would be nice to see these go away.
</p>
<p>
Also, I suspect it may have more subtle issues since the <tt>!</tt> tag can be redefined in a %TAG directive. I haven't tested it but does libyaml take that into account here? Maybe it does, but I could see that easily being overlooked since the <tt>!</tt> isn't needed in the first place.
</p>
Resultshttp://pyyaml.org/ticket/196#changeloghttp://pyyaml.org/ticket/204
http://pyyaml.org/ticket/204#204: In pure-python implementation yaml.load cannot read files generated by yaml.dump/safe_dump when allow_unicode=TrueSat, 01 Oct 2011 22:13:58 GMTkpp.live@…<p>
Consider we're running:
</p>
<pre class="wiki">Jython 2.5.1+ (Release_2_5_1, Aug 4 2010, 07:18:19)
[OpenJDK 64-Bit Server VM (Sun Microsystems Inc.)] on java1.6.0_23
Type "help", "copyright", "credits" or "license" for more information.
&gt;&gt;&gt; import yaml; yaml.__version__
'3.10'
&gt;&gt;&gt; f = file('tmp.yaml', 'wb')
&gt;&gt;&gt; yaml.dump(u'Even just latin in unicode', allow_unicode=True)
"!!python/unicode 'Even just latin in unicode'\n"
&gt;&gt;&gt; yaml.dump(u'Even just latin in unicode', f, allow_unicode=True)
&gt;&gt;&gt; f.close()
&gt;&gt;&gt; f = file('tmp.yaml')
&gt;&gt;&gt; yaml.load(f)
Traceback (most recent call last):
File "&lt;stdin&gt;", line 1, in &lt;module&gt;
File "/usr/share/jython/Lib/site-packages/yaml/__init__.py", line 69, in load
File "/usr/share/jython/Lib/site-packages/yaml/loader.py", line 34, in __init__
File "/usr/share/jython/Lib/site-packages/yaml/reader.py", line 85, in __init__
File "/usr/share/jython/Lib/site-packages/yaml/reader.py", line 135, in determine_encoding
File "/usr/share/jython/Lib/site-packages/yaml/reader.py", line 169, in update
File "/usr/share/jython/Lib/site-packages/yaml/reader.py", line 143, in check_printable
yaml.reader.ReaderError: unacceptable character #x0000: special characters are not allowed
in "tmp.yaml", position 16
</pre><p>
In cpython (with yaml with c-extension) yaml.load works with this file.
</p>
Resultshttp://pyyaml.org/ticket/204#changeloghttp://pyyaml.org/ticket/239
http://pyyaml.org/ticket/239#239: Using yaml.dump() after yaml.load() creates different document for block and folded literalsWed, 09 May 2012 10:45:14 GMTceremcem@…<p>
Hi,
</p>
<p>
With folded and block scalars, a document can not be loaded into python code and then dumped as the same. Why?
</p>
<p>
What I expect is like that:
</p>
<pre class="wiki"># original document
a: |
this is an
example
block
b: &gt;
this is another
example
block
</pre><p>
Using this code:
</p>
<pre class="wiki">f = open(original_document)
result = yaml.dump(yaml.load(f.read()))
f.write(result)
</pre><p>
Expected result:
</p>
<pre class="wiki"># expected result document
a: |
this is an
example
block
b: &gt;
this is another
example
block
</pre><pre class="wiki"># real result
a: 'this is an
example
block
'
b: 'this is another example block
'
</pre><p>
Yes, there are some other questions on the web (<a class="ext-link" href="http://stackoverflow.com/questions/8640959/how-can-i-control-what-scalar-form-pyyaml-uses-for-my-data"><span class="icon"> </span>http://stackoverflow.com/questions/8640959/how-can-i-control-what-scalar-form-pyyaml-uses-for-my-data</a>) but accepted answers does not satisfy my needs.
</p>
<p>
Am I missing something?
</p>
Resultshttp://pyyaml.org/ticket/239#changeloghttp://pyyaml.org/ticket/247
http://pyyaml.org/ticket/247#247: PyYaml uses int instead of size_t in extTue, 12 Jun 2012 01:49:16 GMTdebian@…<p>
<a class="missing wiki">PyYaml?</a> fails to build on the s390x architecture. It seems this is due to using int where the libyaml API uses size_t. The attached patch has been applied in Debian and Ubuntu and resolves the issue.
</p>
Resultshttp://pyyaml.org/ticket/247#changelog