I agree that this is unexpected. It can be fixed by internally passing
more data into the parser before generating the "end" parse event, i.e.
by waiting for the tail text to end before yielding the element that
owns it.
** Changed in: lxml
Importance: Undecided => Medium
** Changed in: lxml
When used with the system python3-lxml package, rather than the version
pip installed into a venv:
Python : sys.version_info(major=3, minor=5, micro=2,
releaselevel='final', serial=0)
lxml.etree : (3, 5, 0, 0)
libxml used : (2, 9, 3)
libxml compiled : (2, 9, 2)
