Custom Query (121 matches)
Results (88 - 90 of 121)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #41 | fixed | Patch: Use types module instead of hand crafted entities and type(). | xi | v.haisman@… |
| Description |
Hi, I have a patch that makes PyYAML use types module instead of hand crafted entities and type(). The motivation is that it silences some PyDev? error complains, like methods not having self parameter and such. |
|||
| #40 | worksforme | incomplete dict constructor | xi | dvd@… |
| Description |
Hi all, I'm puzzled by a strange behavior of yaml If you run the attached script you obtain an output like this: {'date': '732638', 'fields': {}, 'guid': '0000010f153544cf8a314808007f000000000001', 'expiration': None} {'date': '732638', 'fields': {'': {}, 'it': {'title': 'Hello World'}}, 'guid': '0000010f153544cf8a314808007f000000000001', 'expiration': None} *Please note the 'fields' value (I wrap the output to increase legibility)* the first line is printed inside this custom constructor function: def news_constructor(loader, node): nodes = loader.construct_mapping(node) print nodes return nodes the second line (the correct one) is the print of the return values of this function Can you help me or explain me this strange behavior? |
|||
| #39 | fixed | yaml.load("") raises an exception | xi | iusty@… |
| Description |
With the latest PyYAML (3.04): $ python
Python 2.4.4 (#2, Oct 19 2006, 23:03:48)
[GCC 4.1.2 20061007 (prerelease) (Debian 4.1.1-16)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import yaml
>>> yaml.load("")
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/local//lib/python2.4/site-packages/yaml/__init__.py", line 66, in load
return loader.get_data()
File "/usr/local//lib/python2.4/site-packages/yaml/constructor.py", line 38, in get_data
return self.construct_document(self.get_node())
File "/usr/local//lib/python2.4/site-packages/yaml/composer.py", line 23, in get_node
return self.compose_document()
File "/usr/local//lib/python2.4/site-packages/yaml/composer.py", line 35, in compose_document
node = self.compose_node(None, None)
File "/usr/local//lib/python2.4/site-packages/yaml/composer.py", line 52, in compose_node
anchor = event.anchor
AttributeError: 'NoneType' object has no attribute 'anchor'
>>>
I think this is a bug - at least it should raise a yaml.scanner.ScannerError?, like yaml.load("'") does, and then it can be easily catched as a malformed stream. Right now, it's hard to deal with this. Thanks, Iustin |
|||
