Qt has an event loop and async http library. I've used it from PyQt with great success.
Show HN: Asynchronous HTTP/2 client for Python 2.7
11–20 of 62 posts
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#12Qt has an event loop and async http library. I've used it from PyQt with great success.
Does it support HTTP/2?
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#13Any specific reason to develop this for Python 2 rather than Python 3?
There's still a lot of existing and new Python 2 code being written. Idealistically we would all be on Python 3, but software is a messy land.
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#14Qt has an event loop and async http library. I've used it from PyQt with great success.
This other th2c library is MIT licensed, that might be appreciated by some people.
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#15Why Python 2 and not Python 3? Short answer is: because Python 3 already benefits from a better, more complete client: aioh2 ( https://github.com/decentfox/aioh2 ) that works with Python's asyncio. th2c is mostly intended for Tornado backends, trying to keep a similar interface and compatibility with Request / Response objects. It was initially developed in order to be able to communicate with APNS from a python 2.7…
How does that compare to aiohttp? What are the benefits?
I'm not sure I understand the question, are you interested in comparing tornado and aiohttp?
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#16I’m of the opinion that one should only maintain python2 projects not actively develop and expand them. If your project needed http2 then it should be ported to python3.
Edit: would using python3 in a container make sense where the distribution only ships legacy python?
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#17Its name made me think of THC. I'll ask the obvious question: why not Python 3?
Well, Python 3 already has a similar library that deals with this stuff, such as https://github.com/decentfox/aioh2 . Also, this is mostly intended for Tornado backends, offering compatibility with Tornado's request / response objects.
Are people really still so closely wedded to Python 2 that they find it easier to reimplement all the features they need from Python 3 in the former, instead of switching to the latter?
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#18I’m of the opinion that one should only maintain python2 projects not actively develop and expand them. If your project needed http2 then it should be ported to python3. Edit: would using python3 in a container make sense where the distribution only ships legacy python?
What if a company has a large codebase that's in Python 2 and wants http2? Will those suggesting porting help them bear the costs and manhours it takes?
(Google, for one, still uses 2. As does Dropbox. And both companies had Guido Van Rossum working for them at some point).
Re: Show HN: Asynchronous HTTP/2 client for Python 2.7
#19Earlier quoted context omitted.
Well, Python 3 already has a similar library that deals with this stuff, such as https://github.com/decentfox/aioh2 . Also, this is mostly intended for Tornado backends, offering compatibility with Tornado's request / response objects.
Are people really still so closely wedded to Python 2 that they find it easier to reimplement all the features they need from Python 3 in the former, instead of switching to the latter?
Yes.