Custom Query (121 matches)
Results (4 - 6 of 121)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #28 | worksforme | Incorrect handling of strings with trailing spaces | xi | yang |
| Description |
The following fails because the trailing space is dropped. I don't know if this is incorrect dumping (should've quoted), loading (should not have ignored the space), or even both. s = 'abc ' assert syck.load( syck.dump(s) ) == s |
|||
| #35 | worksforme | test program crashes on test file with multiple documents | xi | roel _ dot _ vanhout _ at _ gmail _ dot _ com |
| Description |
The run-parser.c test file crashes on the following test document: ============START================ --- - Harry Potter and the Prisoner of Azkaban - Harry Potter and the Goblet of Fire - Harry Potter and the Order of the Phoenix --- - Memoirs Found in a Bathtub - Snow Crash - Ghost World =============END================= Crash in is api.c, line 604 of the release tarball:
==> yaml_free(token->data.scalar.value);
When I comment out the second document of the test file (from the second '---' on down), it runs fine. |
|||
| #38 | worksforme | PySyck handles non-alphanumeric strings as references, others not | xi | thomas@… |
| Description |
>>> 'a' is 'a' True >>> 'a.' is 'a.' True >>> syck.dump(['a', 'a']) '--- \n- a\n- a\n' >>> syck.dump(['a.', 'a.']) '--- \n- &id001 a.\n- *id001\n' >>> the first two commands show that python itself doesn't distinguish. This is especially problematic since the second case produces a segmentation fault when using syck-0.55-r3 (and surely other older versions). |
|||
