adrenaline VS requests

Here's where you can try it out: https://useadrenaline.com

You may like this: https://github.com/shobrook/adrenaline

User interface is modeled of Adrenaline, I made BlessingAI. An assistant that helps you quickly learn about codebases without having to spend hours search through code. Ask what you would like to know/learn about the codebases and it will answer. Use this if you want to quickly learn about a cool project without manually searching through code.

Lien: [https://useadrenaline.com/

https://useadrenaline.com tries to accomplish this.

Small correction, the correct (and clickable) link is: https://useadrenaline.com/

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.