Repository navigation
Improve README with the differentiators from other HTTP clients #207
Description
See: https://twitter.com/cooperlees/status/1161466340286185472
We're doing awesome things, we should make sure users know why they should use our library. :)
Reacted by Felipe Rodrigues, Anshul Chauhan, Florimond Manca, raphaelauv and byehack
Activity
fbidu commentedon Aug 14, 2019
Do you think it would be better to provide something like a comparison table or some code samples right on the readme comparing the alternatives?
sethmlarson commentedon Aug 15, 2019
Would be nice to answer the question "Why HTTPX versus A, B, or C?" better in the README. Even if it's just a small section.
lovelydinosaur commentedon Aug 25, 2020
Copying this from #1216 so that we've got some better context here...
The notable candidates here are
requests,urllib3,aiohttp, andasks.Main headliners here for HTTPX are...
(And some other stuff that's out on the horizon, too)
They're not the same project because we were approaching a whole bunch of complex areas (such as how to build an HTTP client that supports both sync + async usages) that needed a clean slate, and the freedom to iterate on the design.
However we've put a stack of effort into making sure that the low-level transport layer is really tightly spec'ed as a standalone package -
httpcore. Something we'd be very interested in would be figuring out with other projects if there's any mileage in figuring out if their clients would be able to usehttpcoreas their transport layer. In order to:We've not really reached out to folks about that yet since we've been focusing on getting to a 1.0 release first, but it might be an area worth exploring.
stale commentedon Feb 20, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
lovelydinosaur commentedon Feb 21, 2022
Still valid thx, @Stale bot.
stale commentedon Mar 25, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon Oct 15, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.