Your message dated Sun, 23 Aug 2009 11:22:29 +0100
with message-id <[email protected]>
and subject line Package python-syck has been removed from Debian
has caused the Debian Bug report #293084,
regarding Characters not serialized correctly by syck
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
293084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293084
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-syck
Version: 0.42-5
Hello again!
After trying to use ydump/syck some more, I ran into the problem that
'?' characters aren't escaped correctly, it seems. I decided to write a
short program to try all the ASCII characters and see which don't work:
import syck, ydump
for i in xrange(128):
c = chr(i)
try:
assert syck.load(ydump.dump(c)) == c
except:
print "failed for chr(%d) = '%s'" % (i,c)
On my computer, this generates:
failed for chr(0) = ''
failed for chr(10) = '
'
failed for chr(32) = ' '
failed for chr(33) = '!'
failed for chr(44) = ','
failed for chr(62) = '>'
failed for chr(63) = '?'
failed for chr(91) = '['
failed for chr(93) = ']'
failed for chr(123) = '{'
failed for chr(124) = '|'
failed for chr(125) = '}'
failed for chr(126) = '~'
(These may look familiar: they have special meanings in YAML, and are
listed on the YAML reference card at <http://yaml.org/refcard.html>.)
I think this could be fixed (as before) by simply adding these
characters to the needsSingleQuote() function; a simple (but probably
not optimal) way to do it would be to add the lines:
if data[0] in ['\n',' ','!',',','>','?','[',']','{','|','}','~']:
return 1
(chr(0) seems to be dumped correctly, but Syck refuses to load a string
that contains '\0'. I have no idea know how hard this would be to fix.
I'll file a separate bug for this.)
While I'm at it, I tried putting other special names from the YAML
reference card through syck/ydump, and these also failed:
- 'null' (upper-, lower-, and title-case only)
- '.inf' (upper-, lower-, and title-case only)
- '.nan' (upper-, lower-, and title-case only)
These should also be fairly easy to fix in needsSingleQuote().
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages python-syck depends on:
ii python 2.3.4-6 An interactive high-level
object-o
ii python2.3-syck 0.42-5 YAML parser kit -- Python
2.3 bind
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.61.2-1+rm
You filled the bug http://bugs.debian.org/293084 in Debian BTS
against the package python-syck. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/540566. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
--- End Message ---
