> issue is resolved when using bs4==4.10.0
Thanks for investigating. That means that it's no longer an issue then, right?
Closing this as a third-party issue.
** Changed in: lxml
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hmm, looks like the functions are registered in the wrong order: local
first, then global, then EXSLT. Local functions should take precendence.
PR welcome, see the _XPathContext class in "xpath.pxi".
** Changed in: lxml
Importance: Undecided => Low
** Changed in: lxml
Status: New =>
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
That's unrelated to this ticket. It's due to incorrect usage of
iterparse(). Please read the documentation. Passing a parser into
iterparse() is not possible and the second argument of iterparse() is
not for what the author of the code apparently thinks it is.
** Changed in: ubuntu
And while at it, I'd also recommend upgrading to 2.3.6. It contains
several crash bug fixes. I guess 3.2.1 is out of scope for Ubuntu 12.04.
http://lxml.de/2.3/changes-2.3.6.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
