lxml.etree.parse raises UnicodeDecodeError instead of IOError

Bug #712941 reported by griph on 2011-02-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxml
Medium
scoder

Bug Description

lxml.etree.parse should give IOError if applied to non-existent
path. If lxml.etree.parse is given a path containing characters beyond latin-1,
it gives UnicodeDecodeError instead. That hides original cause of an
exception.

Versions:

Python : (2, 6, 2, 'final', 0)
lxml.etree : (2, 2, 8, 0)
lxml.etree : (2, 7, 7)
lxml.etree : (2, 7, 7)
lxml.etree : (1, 1, 26)
lxml.etree : (1, 1, 26)

griph (griph) wrote :
scoder (scoder) wrote :
Changed in lxml:
assignee: nobody → scoder (scoder)
importance: Undecided → Medium
status: New → Fix Committed
scoder (scoder) wrote :

Fixed in lxml 3.2.0.

Changed in lxml:
status: Fix Committed → Fix Released
scoder (scoder) on 2013-04-28
Changed in lxml:
milestone: none → 3.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers