webtraversallibrary VS requests-html

TL;DR: Dataset, pre-print with comparisons of NN architectures for the Web, useful library for Web manipulation

2) If interacting with the Web is more your thing, you can also check out the WebTraversalLibrary which you can use to easily script agents that interact with the Internet via a browser. This library provides extremely useful abstractions so that you don't have to worry about writing the code to interact with the low-level implementations of the browser at all (it abstracts the browser up to a state/action level so all you have to do is worry about the RL part). You can find quite a few example scripts in the repo.

If you're looking for something that simplifies the use of selenium, check out Web Traversal Library: https://github.com/klarna-incubator/webtraversallibrary

Wrote an abstraction layer for easier work with web automation, especially with machine learning: https://github.com/klarna-incubator/webtraversallibrary

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.