requests-futures VS urllib3

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

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

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).

This error is coming from Python, it's telling us Python is failing to import the urllib3 library, these lines here are important:

Requests allows you to send HTTP/1.1 requests extremely easily. There’s no need to manually add query strings to your URLs, or to form-encode your POST data. Keep-alive and HTTP connection pooling are 100% automatic, thanks to urllib3.

Judging projects based on stars is really immature. for example everyone knows requests https://github.com/psf/requests the python package that is used in every python project out there. it has 47k star too WOW. but the thing that less people know is urllib3. https://github.com/urllib3/urllib3. it has only 3k stars. It basically does the heavy lifting for requests!!

urllib3 – Python HTTP library with thread-safe connection pooling, file post support, user friendly, and more

I'm not really clear on how to find out what issues have currently active bounties attached to them. I followed some links to this github query: https://github.com/urllib3/urllib3/issues?q=is%3Aopen+is%3Ai...

but all I see there are issues that appear to have already been paid for.

(I've chopped it down a bit to emphasise the important bits)

But then I looked at upstream and I notice they've added type annotations, which do greatly improve things:

https://github.com/urllib3/urllib3/blob/e16beb210c03c6f5ce4e...

    def _new_conn(self) -> socket.socket:

You have somehow installed an extremely old version of urllib3. It looks like the selectors module was deleted in 2018.

I've found httpx to be very approachable for my API consumption tasks and less wordy than urllib3.

Here are the docs if you're interested: https://urllib3.readthedocs.io

Some context on David Lord's entry, he was our first attempt to pay a community member to contribute a PR and get paid for the contribution. Here's the PR we merged and paid him for: https://github.com/urllib3/urllib3/pull/2257