[New-bugs-announce] [issue19609] Codec exception chaining shouldn't cover the initial codec lookup

Nick Coghlan report at bugs.python.org
Fri Nov 15 12:10:29 CET 2013


New submission from Nick Coghlan:

The exception chaining from issue 17828 is triggering for the initial codec lookup. This is less than helpful:

====================
Failed example:
    str(result)
Expected:
    Traceback (most recent call last):
      ...
    LookupError: unknown encoding: UCS4
Got:
    LookupError: unknown encoding: UCS4
    <BLANKLINE>
    The above exception was the direct cause of the following exception:
    <BLANKLINE>
    Traceback (most recent call last):
      File ".../py3km/python/lib/python3.4/doctest.py", line 1291, in __run
        compileflags, 1), test.globs)
      File "<doctest xpathxslt.txt[89]>", line 1, in <module>
        str(result)
      File "xslt.pxi", line 727, in lxml.etree._XSLTResultTree.__str__
(src/lxml/lxml.etree.c:143584)
      File "xslt.pxi", line 750, in lxml.etree._XSLTResultTree.__unicode__
(src/lxml/lxml.etree.c:143853)
    LookupError: decoding with 'UCS4' codec failed (LookupError: unknown
encoding: UCS4)
====================

----------
assignee: ncoghlan
messages: 202937
nosy: ncoghlan
priority: normal
severity: normal
status: open
title: Codec exception chaining shouldn't cover the initial codec lookup
versions: Python 3.4

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


More information about the New-bugs-announce mailing list