Httpx: A next-generation HTTP client for Python • Hacker News Board

dragonwriter wrote: post #77

greglindahl wrote: post #76

Earlier quoted context omitted.

I want to mess with certs in Python so that my web crawler can actually access the whole web. If you don't talk to a wide variety of hosts, you probably haven't noticed that it's broken for 1%.

If you work in a corporate environment, you would probably notice that systems that insist on bundling their own certs without an easy to activate option of using system cert store are broken. (And even if the library has an easy to use option, if it's easy to not expose it, much software built on the library will still be broken.) People should be empowered to substitute cert stores, but the system store should be t…

Why yes, my web crawler operates in a corporate environment. It's almost as if different companies have different needs.

Re: Httpx: A next-generation HTTP client for Python

#84

Post by toyg » Sat, Jan 11, 2020, 2:46 AM UTC

bproven wrote: post #74

looks nice, but appears to have a quite a few third party deps that requests doesnt?

Requests simply vendors what it needs, afaik. Which is sub-optimal. At least this gives you visibility into those deps.

Re: Httpx: A next-generation HTTP client for Python

#85

Post by EamonnMR » Sat, Jan 11, 2020, 4:03 AM UTC

tiangolo wrote: post #22

FastAPI creator here... if you use FastAPI, HTTPX would probably be the best match for sending requests, just saying... :D

Thanks for the tip, we'll be sure to try it. And thanks for the framework!

Re: Httpx: A next-generation HTTP client for Python

#86

Post by jordic » Sat, Jan 11, 2020, 4:20 AM UTC

westurner wrote: post #31

jordic wrote: post #23

Earlier quoted context omitted.

The huge win against requests is that Https is fully async.. you can download 20 files in parallel without not too much effort. Throughout in python asyncio is amazing, something similar to node or perhaps better... That's the main point.

FWIW, requests3 has "Type-annotations for all public-facing APIs", asyncio, HTTP/2, connection pooling, timeouts, etc https://github.com/kennethreitz/requests3

Sorry, have you checked the source? Are these features there or only announced? Has requests added a timeout by default finally?

Re: Httpx: A next-generation HTTP client for Python

#87

Post by westurner » Sat, Jan 11, 2020, 4:45 AM UTC

jordic wrote: post #86

westurner wrote: post #31

Earlier quoted context omitted.

FWIW, requests3 has "Type-annotations for all public-facing APIs", asyncio, HTTP/2, connection pooling, timeouts, etc https://github.com/kennethreitz/requests3

Sorry, have you checked the source? Are these features there or only announced? Has requests added a timeout by default finally?

It looks like requests is now owned by PSF. https://github.com/psf/requests

But IDK why requests3 wasn't transferred as well, and why issues appear to be disabled on the repo now.

The docs reference a timeout arg (that appears to default to the socket default timeout) for connect and/or read https://3.python-requests.org/user/advanced/#timeouts

And the tests reference a timeout argument. If that doesn't work, I wonder how much work it would be to send a PR (instead of just talking s to Ken and not contributing any code)

Re: Httpx: A next-generation HTTP client for Python

#88

Post by rajasimon » Sat, Jan 11, 2020, 5:27 AM UTC

bbmario wrote: post #13

I know this is unrelated, but probably a lot of Pythonistas here and I've been wondering: what is the async web framework of choice for you guys today? As for DBs, still SQLAlchemy? What about a prettier (js) alternative?

Django + Channels

Re: Httpx: A next-generation HTTP client for Python

#89

Post by jordic » Sat, Jan 11, 2020, 7:12 AM UTC

westurner wrote: post #87

jordic wrote: post #86

Earlier quoted context omitted.

Sorry, have you checked the source? Are these features there or only announced? Has requests added a timeout by default finally?

It looks like requests is now owned by PSF. https://github.com/psf/requests But IDK why requests3 wasn't transferred as well, and why issues appear to be disabled on the repo now. The docs reference a timeout arg (that appears to default to the socket default timeout) for connect and/or read https://3.python-requests.org/user/advanced/#timeouts And the tests reference a timeout argument. If that doesn't work, I wonde…

>But IDK why requests3 wasn't transferred as well, and

That's thing... Who knows..

Re: Httpx: A next-generation HTTP client for Python

#90

Post by hypewatch » Sat, Jan 11, 2020, 7:22 AM UTC

I’ve used httpx to test server load issues for our most sensitive system and it works exactly how you’d expect it would. Highly recommend it.