Closed wku closed 5 years ago
As Curio does not have any HTTP support in the core, I'm not sure how this bug report applies. Is curio_http a separate package?
Yes I understood the question asked, in the wrong place.
Is it planned, in the near future, HTTP support in the core? This would increase the amount of community.
From the readme:
Q: Is curio going to evolve into a framework?
A: No, because evolving into a framework would mean modifying curio to actually do something. If it actually did something, then people would start using it to do things. And then all of those things would have to be documented, tested, and supported. People would start complaining about how all the things related to the various built-in things should have new things added to do some crazy thing. No forget that. Curio remains committed to not doing much of anything the best it can. This includes not implementing HTTP.
There are ioless http libraries out there. You can use them.
How to implement work through a proxy server? And the ability to change the proxy for each new conversion
async def fetch_one(url): async with curio_http.ClientSession() as session: proxies = { 'http': '162.244.134.196:8080', 'https': '162.244.134.196:8080', } response = await session.get(url, proxies=proxies)