Custom Query (121 matches)
Results (64 - 66 of 121)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #46 | worksforme | syck.dump is not here ! | xi | jean.philippe.mague _at_ gmail _d.o.t_ com |
| Description |
when installing pysyck from syck-0.61+svn231+patches.tar.gz, I end up with a module with only the Node type and the load function (and several blah funtions). When I install it from PySyck-0.61.2.tar.gz (with syck previouly installed) every goes just fine. I use python 2.4 on a Ubuntu Edgy |
|||
| #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 |
|||
| #74 | fixed | porting yaml to python 3000 | xi | idadesub@… |
| Description |
Hello, 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:
try:
set
except NameError:
from sets import Set as set
Finally, in case it wasn't clear in the patch, I've removed the following tests: D tests/data/construct-python-unicode-utf8.data D tests/data/construct-python-unicode-ascii.data D tests/data/construct-python-unicode-utf8.code D tests/data/construct-python-unicode-ascii.code And added: A tests/data/construct-python-bytes-utf8.data A tests/data/construct-python-bytes-ascii.data A tests/data/construct-python-bytes-utf8.code A tests/data/construct-python-bytes-ascii.code |
|||
