As the author of Beautiful Soup let me say that I would probably prefer the new behavior. I haven't been able to get CDATA sections from lxml the way I have been from html.parser and html5lib.
I say I'd _probably_ prefer the new behavior because the way in which the CDATA section is being sent over -- as chunked data blocks -- means I don't think I can recognize it as CDATA and create a special CData object on my side. But I'd definitely rather have the data than not.
As the author of Beautiful Soup let me say that I would probably prefer the new behavior. I haven't been able to get CDATA sections from lxml the way I have been from html.parser and html5lib.
I've been using the strip_cdata=False argument mentioned here: /lxml.de/ api.html# cdata
https:/
But in the context in which I'm using it, it's never worked: /bugs.launchpad .net/beautifuls oup/+bug/ 1275085
https:/
I say I'd _probably_ prefer the new behavior because the way in which the CDATA section is being sent over -- as chunked data blocks -- means I don't think I can recognize it as CDATA and create a special CData object on my side. But I'd definitely rather have the data than not.