[benatkin]

Its name made me think of THC.

I'll ask the obvious question: why not Python 3?

[vsmhn]

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.

[benatkin]

I see. May I suggest linking to that in the README? And if you aren't part of the Python 2 forever camp, suggest how one might migrate from using your library to using python 3 with the other library in the future? And if the APIs aren't similar it might be a good idea to make them similar.

[vsmhn]

I understand your point, and I'll try to update the README with that information. However, this client tries to follow Tornado's ways, whereas aioh2 works on Python's asyncio.

It's still WIP, so feedback like yours helps a lot, thanks!

[peterkelly]

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?

[siimtalvik]

yes.

I had a coworker who was against moving to python3(and kept on writing python2 code for a while) because you need to use brackets with python3 print statement.

[coldtea]

Yes.

[always_good]

Just think of any large code base and it should be obvious.

What's simpler, rewriting a massive project, or maintaining a library? For example, OP did the latter himself.