[vsmhn]

Why 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 environment.

[k1ns]

Hey, I posted an issue on the repo for a Python 3 port here: https://github.com/vladmunteanu/th2c/issues/27. I think you should give the same explanation there as you did here and close it outright as what you said makes sense. There is still a lot of Python 2.x code being written out there with companies looking for quick ways to upgrade their stack. While I wish it weren't so, your point makes a lot of sense.

[ericfrederich]

How does that compare to aiohttp? What are the benefits?

[vsmhn]

I'm not sure I understand the question, are you interested in comparing tornado and aiohttp?

[omginternets]

aio isn't available for py2. The benefit is that this is available for py2.

[loeg]

There is https://github.com/vstinner/trollius for vanilla Python2.

[vsmhn]

trollius is no longer maintained

[loeg]

It's still a reasonable starting place for anyone wanting asyncio on vanilla Python2. Outside of vanilla Python2, Tauthon also has some tracking issues for the language extensions and libraries needed for a backport of asyncio to Tauthon.[0]

[0]: https://github.com/naftaliharris/tauthon/issues/10