[New-bugs-announce] [issue5432] plistlib contains unescaped hex sequence in doc string

Jim Correia report at bugs.python.org
Fri Mar 6 19:53:41 CET 2009


New submission from Jim Correia <jim.correia at pobox.com>:

The module doc string contains an example with hex escape sequences (see 
below). They are converted to their literal values by pydoc, which 
results in an unexpected encoding for the output of pydoc.

(raw string, or proper escaping solves the problem)

Relevant chunk of the file:

            anotherString="<hello & hi there!>",
            aUnicodeValue=u'M\xe4ssig, Ma\xdf',
            aTrueValue=True,
            aFalseValue=False,
        ),
        someData = Data("<binary gunk>"),
        someMoreData = Data("<lots of binary gunk>" * 10),
        aDate = 
datetime.datetime.fromtimestamp(time.mktime(time.gmtime())),
    )
    # unicode keys are possible, but a little awkward to use:
    pl[u'\xc5benraa'] = "That was a unicode key."

----------
components: Library (Lib)
messages: 83251
nosy: jim.correia
severity: normal
status: open
title: plistlib contains unescaped hex sequence in doc string
versions: Python 2.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5432>
_______________________________________


More information about the New-bugs-announce mailing list