I'm curious why one would suggest using this over the built-in ThreadPoolExecutor class?
Here's a complete, similar example from the Python docs: https://docs.python.org/3/library/concurrent.futures.html#th....
Granted that example is more lines of code than the README for this library. But the core of it is fairly straightforward:
rsps = []
with concurrent.futures.ThreadPoolExecutor(max_workers=N) as executor:
futures = [executor.submit(requests.get, url) for url in urls]
for future in concurrent.futures.as_completed(futures):
rsps.append(future.result)