Custom Query (132 matches)


Show under each result:

Results (34 - 36 of 132)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#62 fixed value token of single period ('.') is parsed incorrectly, throws wrong exception xi sproaticus

Reported by sproaticus, 7 years ago.


A scalar value token consisting of just a period ('.') is interpreted as a float value. When construct_yaml_float() creates a float using this value, it throws an uncaught ValueError instead of yaml.YAMLError

(Also, what's PIL doing in the stack? I didn't import it.)

>>> yaml.load('yaml: .')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.5/site-packages/PIL/", line 66, in load
  File "build/bdist.linux-i686/egg/yaml/", line 38, in get_data
  File "build/bdist.linux-i686/egg/yaml/", line 46, in construct_document
  File "build/bdist.linux-i686/egg/yaml/", line 394, in construct_yaml_map
  File "build/bdist.linux-i686/egg/yaml/", line 207, in construct_mapping
  File "build/bdist.linux-i686/egg/yaml/", line 132, in construct_mapping
  File "build/bdist.linux-i686/egg/yaml/", line 87, in construct_object
  File "build/bdist.linux-i686/egg/yaml/", line 281, in construct_yaml_float
ValueError: invalid literal for float(): .


  • Python 2.5.1 (r251:54863, May 2 2007, 16:56:35) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2
  • PyYAML-3.05-py2.5.egg
#64 fixed yaml.dump and indentation: xi…

Reported by…, 7 years ago.


In python, when I have :

y = {'x' : 3, z : [{'val' : 3}, {'val' : 4}]} yaml.dump(y, default_flow_style=False)

The result is: 'x: 3\nz:\n- val: 3\n- val: 4\n'

I believe there should be a space before each hypen.



#74 fixed porting yaml to python 3000 xi idadesub@…

Reported by idadesub@…, 6 years ago.



I've started to play around with porting code over to python 3, and since I use yaml, I had to port it over as well. So, here's the patch :) It's pretty heavyweight, though, because of the change of "str" to be unicode. Since there are many incompatible changes, I'd recommend creating a branch for this.

Here's some other notes that you ought to be aware of:

  • In order to do from error import * you now have to specify the full path to the module from yaml.error import *, explicitly specify what you want to import with from .error import YAMLError, or from . import error. I went with from yaml.error import * as that let me touch less code.
  • Removed:
except NameError:
    from sets import Set as set
  • Removed utf_*_decode functions from yaml/
  • file was removed as a function, so I replaced it with open.
  • Since python 3 doesn't have classic-style classes, I removed all the instance code I could find. This means that __initargs__ isn't used anymore.
  • u'...' isn't supported, so it's been replaced with just '...'.
  • Unicode encoding now is str to bytes and decoding is bytes to str, so it required a lot of changes to change the order of encoding and decoding.
  • unichr was replaced with chr.
  • print now requires parenthesis.
  • open('foo', 'rb') now returns a stream object that produces bytes instead of strs, so that had to be specially handled.
  • Automatic tuple extraction with things like def foo(a, b, (c, d)): ... is no longer supported.
  • There is no longer total ordering of all types, so [None, 1].sort() is now a TypeError. So, I added a basic __lt__ to yaml.nodes.Node which might need more attention.
  • exec now requires parenthesis. Also, it doesn't seem like the values that get added to locals() are actually added to the local scope. This might be a bug.
  • StringIO has been moved to the io module.
  • Catching exceptions is now written like except YAMLError as exc.
  • If you catch and then re raise another exception you can write raise YAMLError from other_exception to save the history of the other exception.
  • I left in support for !!python/long and !!python/unicode for backwards compatibility.
  • I removed all the (object) from class definition.
  • mapping.keys() now returns an iterator, so I wrapped all the cases I could find that require it returning a list.
  • I moved the sorting of a mapping to after the items in it have been turned into nodes so that it's more sortable.

Finally, in case it wasn't clear in the patch, I've removed the following tests:

D      tests/data/
D      tests/data/
D      tests/data/construct-python-unicode-utf8.code
D      tests/data/construct-python-unicode-ascii.code

And added:

A      tests/data/
A      tests/data/
A      tests/data/construct-python-bytes-utf8.code
A      tests/data/construct-python-bytes-ascii.code
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.