etree.xmlfile shadows exceptions thrown by output
Bug #1415643 reported by
dhjt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxml |
Fix Released
|
Undecided
|
scoder |
Bug Description
It looks like lxml eats any exceptions in the output that etree.xmlfile
writes into, leaving the output in a broken state. This goes unnoticed.
Only if you try to write to that same output again, things explode.
Please refer to attached testcase and the mailing list:
https:/
System info:
Python : sys.version_
releaselevel=
lxml.etree : (3, 4, 0, 0)
libxml used : (2, 9, 1)
libxml compiled : (2, 7, 8)
libxslt used : (1, 1, 28)
libxslt compiled : (1, 1, 26)
Changed in lxml: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Rejecting as it's essentially fixed in Py3.