Closed Cokemonkey11 closed 5 years ago
My current guess is that this is related to changes between lxml 3 and lxml 4 given that I do see that attribute existing, and I'm using lxml 4.2.5 in my environment. Could you try upgrading to lxml 4.2.5 to see if that resolves this? If so, I can just update the requirements.txt
file to require a newer version.
Updating lxml
to 4.2.5 is harmless enough that I've now increased our minimum version requirement to hopefully avert the problem you encountered earlier. Thanks for your bug report!
Seems to be a small hole in error handling?
Thanks for your work on this!