This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: plistlib contains unescaped hex sequence in doc string
Type: Stage:
Components: Library (Lib) Versions: Python 2.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, jim.correia
Priority: normal Keywords:

Created on 2009-03-06 18:53 by jim.correia, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg83251 - (view) Author: Jim Correia (jim.correia) Date: 2009-03-06 18:53
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."
msg85515 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-04-05 15:14
Fixed in r71243, thanks!
History
Date User Action Args
2022-04-11 14:56:46adminsetgithub: 49682
2009-04-05 15:14:40georg.brandlsetstatus: open -> closed

nosy: + georg.brandl
messages: + msg85515

resolution: fixed
2009-03-06 18:53:40jim.correiacreate