Custom Query (132 matches)
Results (46 - 48 of 132)
|#132||worksforme||PySyck does not dump dictionaries||xi||xl269@…|
infinity0@xl269:~$ uname -a Linux xl269 2.6.30-1-amd64 #1 SMP Sun Jun 14 15:00:29 UTC 2009 x86_64 GNU/Linux infinity0@xl269:~$ python --version Python 2.5.4 infinity0@xl269:~$ python Python 2.5.4 (r254:67916, Feb 18 2009, 03:00:47) [GCC 4.3.3] on linux2 Type "help", "copyright", "credits" or "license" for more information.
|#38||worksforme||PySyck handles non-alphanumeric strings as references, others not||xi||thomas@…|
>>> '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).
|#33||fixed||PyYAML + libyyaml shouldn't need PyRex||xi||edemaine@…|
In my understanding of PyRex? (which, I admit, is fairly limited), it is a tool that converts PyRex? code into C (.c, .h, etc.) and Python code. Can't this conversion be done ahead of time when assembling a distribution, so that you don't need PyRex? on the install side? (Same as running lex or yacc etc. at distribution time instead of install time.) Or is there something more subtle going on during installation that this is actually necessary?
Reducing the barrier to installation should make the "fast PyYAML solution" (PyYAML + libyaml) more widely available.