requests-futures VS kiss-headers

- https://github.com/ross/requests-futures

For the simple one-off case, check out requests-futures or requests-threads

Lately I tried https://github.com/ross/requests-futures and it is really nice little wrapper for requests library that makes it run asynchronous via thread pool. Worth checking out if you are already using requests lib.

requests-futures can handle that

Thank you, I didn’t know about this before. Looks like either requests-threads or requests-futures can do the job. Not sure how I can add async and await to the script above, I’ll tinker around with it later!

I found examples of running parallel async http requests using grequests, but in its GitHub page it recommends using requests-threads or requests-futures instead. Which of them would be the most straightforward tool for optimizing a sequence of GET requests against an API. Case scenario: API endpoint provides paginated responses. With first response, I get the total of itens, which allow me to prepare all the remaining urls. The API allows for 25 simultaneous requests from a single user session (JWT token).

I would suggest using a session in requests if you're not already but also to look at asyncio/aiohttp , requests-futures or requests-html which can be used asynchronously and is written by the author of the requests library.