[lxml] Re: tostring() returning possible invalid XML. Is this a bug?

On 7 Jun 2022, at 16:56, brian.bird@trustpayments.com wrote:

In more recent versions of lxml the tostring() method can return extra text after the closing tag of the node I've passed to it. So instead of returning

b'\n\n'

it returns

b'\n\n\n\n'

This looks **a lot** like this https://mail.python.org/archives/list/lxml@python.org/thread/LCTOSIIWGGALAMS... Can you update your version of libxml2? Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Sengelsweg 34 Düsseldorf D- 40489 Tel: +49-203-3925-0390 Mobile: +49-178-782-6226