lxml.etree.parse raises UnicodeDecodeError instead of IOError
Bug #712941 reported by
griph
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lxml |
Fix Released
|
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)
Revision history for this message
| griph (griph) wrote | #1 |
Revision history for this message
| scoder (scoder) wrote | #2 |
| Changed in lxml: | |
| assignee: | nobody → scoder (scoder) |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
Revision history for this message
| scoder (scoder) wrote | #3 |
| Changed in lxml: | |
| status: | Fix Committed → Fix Released |
| Changed in lxml: | |
| milestone: | none → 3.2 |
To post a comment you must log in.
Fixed here:
https:/