3 ms·
Because Requests makes HTTP much easier to work with, which has dramatically expanded the pool of developers who are comfortable doing that kind of work. When w
by passive 7y ago
Because Requests makes HTTP much easier to work with, which has dramatically expanded the pool of developers who are comfortable doing that kind of work.
When we've had to add some level of concurrency to an HTTP tool, we have serious discussions over whether to swap out Requests, or to just run multiple instances of the tool, especially if it's a tool that only requires concurrency sometimes.
This is nothing against aiohttp or others, but Requests is de facto standard library.
- LyndsySimon 7y ago> Requests is de facto standard library. I think a valuable discussion that could come from this is to seek to understand why it’s “de facto” standard library instead of “de jure” standard library. I’ve heard it said that “the standard library is where popular packages go to die”, and I think that’s very true. I’m very happy that Requests isn’t part of the standard library, because that means that updates - including updates that are extremely important to maintaining the health of the library over time - are possible without an entirely separate release of cPython itself.