Gael Pasgrimaud
Gael Pasgrimaud
Looks like lxml is using 2.9.10 in the build process: ``` Preparing to unpack .../11-libxml2-dev_2.9.10+dfsg-5+ubuntu18.04.1+deb.sury.org+3_amd64.deb ... ``` https://github.com/lxml/lxml/runs/2618555701?check_suite_focus=true
And 2.9.12 was released only 6 days ago (and don't seems to introduce major changes). Not sure it's the problem
I guess that's because it doesn't use the same parser See https://github.com/gawel/pyquery/blob/master/pyquery/pyquery.py#L195 `pq(url=url, parser='xml')` should do what you want
I don't think so. It's related to https://github.com/gawel/pyquery/issues/76
I guess there's no such thing because lxml do that
PyQuery is multi-platform May be linking to http://lxml.de/installation.html instead is a better idea
Yes I know. But installation problems always came from lxml. So why having a complex install section when you just need to says "if you experiment problems see this link"...
That's how jQuery works AFAIK
I'ts probably caused by some underlying lxml behaviours. It's always hard to figure. I think that lxml do not print xml headers (doctype) and remove one of the xmlns because...
Yeah the method should be preserved. As I remember it's hard because we use `self.__class__()` a lot. Mean that you may have lost the original method when trying to print...