requests VS urllib3

For many years now, Requests has been frozen. Being left in a vegetative state and not evolving, this blocked millions of developers from using more advanced features.

- Ubiquitous “requests” library used in most docs examples, no async support https://github.com/psf/requests

Explore here.

It's Lukasa (his name is Cory, there's Łukasz in PSF though, but that's a different person). Looking at him, he made significant contributions to the requests repo: https://github.com/psf/requests/graphs/contributors

> I'd love to see the look on some of these people's faces when they find out that tool/software/whatever they use is actually using libcurl under the hood.

Python dependencies (does not include curl)

https://devguide.python.org/getting-started/setup-building/i...

The "requests" module in Python (does not use curl)

https://github.com/psf/requests

This part can be found in the README of the GitHub repository.

Looking around for similar errors I found this issue where they recommended trying to use a newer version of the urllib3 library.

but I appreciate the fact that there is an issue about it, it's acknowledged and .. unfixable, it would now break too many things https://github.com/psf/requests/issues/2002

The requests package has been the golden standard for package structure for as long as I can remember.

As opposed to what the article says, urllib3 now has experimental support for browser as of Jan 30th.

Source: https://github.com/urllib3/urllib3/releases/tag/2.2.0

Then, I tried to get a firm grip on urllib3 base code, contributing this and there until I was ready to kick things up with a proof of concept that would have put urllib3 far ahead. Without any breaking changes. I was delusional. This was a bit of a shock, but six months passed between my initial kick off and my formal give up, and here's why in a nutshell:

Oh wow, thanks for this story! Would love to hear more if you have time :) Good luck with testing it out.

Note that we found an issue w/ emitting an InsecureRequestWarning by default. The request is perfectly secure, it's just we aren't telling the ConnectionPool that information (see: https://github.com/urllib3/urllib3/issues/3331)

I've had a good experience doing a couple of bug fix bounties for urllib3 https://github.com/urllib3/urllib3/issues . I'd be interested in how the maintainers how found running the bug bounty and if it's given them more useful fixes or if it just adds more noise to deal with

ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with LibreSSL 2.8.3. See: https://github.com/urllib3/urllib3/issues/2168

> Could not import extension sphinx.builders.linkcheck (exception: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with OpenSSL 1.0.2n 7 Dec 2017. See: https://github.com/urllib3/urllib3/issues/2168)

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