pyppeteer VS requests-html

The latest version of Pyppeteer, i.e., 1.0.2, can also be installed by executing pip3 install -U git+https://github.com/pyppeteer/pyppeteer@dev on the terminal.

Having async baked into Python both as a keyword and standard library has vastly opened up the number of use cases async will be used in where it is appropriate, one of my favorite libraries pyppeteer would have not existed in the easy nice way it can be used without asyncio: https://github.com/pyppeteer/pyppeteer

Yes, this is scraping. You need a legit new cookie issued by the site. The solution is to automate the going to get the cookies part. The most straight forward way to do this is probably using a headless browser through something like Selenium or pyppeteer.

Last I checked, pyppeteer wasn't a thing anymore, and I haven't tried Playwright but if it has a headless mode, thats what you want so you don't have a browser open.

pip install -U git+https://github.com/pyppeteer/pyppeteer@dev

The normal Puppeteer package is JavaScript, but I do see that there's a Python port called pyppeteer. I can't vouch for it specifically, but I imagine it's similarly easy to use as the JS version.

requests-html

Ya, thanks for advice. When using requests_html library, I am trying to lower down the speed using response.html.render(timeout=1000), but it raise Runtime error instead on Google Colab: https://github.com/psf/requests-html/issues/517.

For dynamic js, prefer requests-html with xpath selection.

Example: requests-html which has a rather exhaustive README.md, but their dedicated page is not that helpful, if I remember correctly, and currently the domain is suspended.

When it comes to web scraping, the usual people recommend is beautifulsoup, lxml, or selenium. But I highly recommend people check out requests-html also. Its a library that is a happy medium between ease of use as in beautifulsoup and also good enough to be used for dynamic, javascript data where it would be overkill to use a browser emulator like selenium.

Quite possible. If you look at requests-html source code, it is simply one single python file that acts as a wrapper around a bunch of other packages, like requests, chromium, parse, lxml, etc., plus a couple convenience functions. So it could easily be some sort of bad dependency resolution.

What I do is try to see if I can use requests_html first before trying selenium. requests_html is usually enough if I dont need to interact with browser widgets or if the authentication isnt too difficult to reverse engineer.