Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Asynchronous HTTP/2 client for Python 2.7

github.com

Post reply on HN
Print view View original

21–30 of 62 posts

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#21

Post by goatlover »

coldtea wrote: post #18
gigatexal wrote: post #16

I’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).

Companies are going to have to port at some point.

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#22

Post by brudgers »

goatlover wrote: post #21
coldtea wrote: post #18

Earlier quoted context omitted.

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).

Companies are going to have to port at some point.

Google has Grumpy. Because writing a compiler is easier than porting. https://github.com/google/grumpy

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#23

Post by k1ns »

gigatexal wrote: post #16

I’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?

Posted an issue here: https://github.com/vladmunteanu/th2c/issues/27

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#24

Post by k1ns »

vsmhn wrote: post #6

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…

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.

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#25

Post by enitihas »

goatlover wrote: post #21
coldtea wrote: post #18

Earlier quoted context omitted.

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).

Companies are going to have to port at some point.

Not sure about that. Some companies may have codebases as complicated as the python codebase itself. For them it may make more sense to maintain python2 than to upgrade. Granted, there will be very few such companies.

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#26

Post by [deleted] »

k1ns wrote: post #24
vsmhn wrote: post #6

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…

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.

[deleted]

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#27

Post by kbutler »

goatlover wrote: post #21
coldtea wrote: post #18

Earlier quoted context omitted.

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).

Companies are going to have to port at some point.

Unjustifiable assertion.

  - they could continue to maintain python2
  - they could move to a non-python platform
  - they could go out of business
  - they could hold out for Python4 (Python3 was only 8 years after Python2)
  ...

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#28

Post by CJefferson »

goatlover wrote: post #21
coldtea wrote: post #18

Earlier quoted context omitted.

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).

Companies are going to have to port at some point.

Python 2 is popular enough that someone will keep up support for decades to come. Just making sure it supports new OS releases, and fixing the occasional bug, will not be a significant overhead.

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#29

Post by CJefferson »

goatlover wrote: post #20
meddlepal wrote: post #13

Earlier quoted context omitted.

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.

It's been ten years, so it's gone beyond "idealistically".

Still not distributed by default on Mac or Ubuntu long term release, unlike 2.

Re: Show HN: Asynchronous HTTP/2 client for Python 2.7

#30

Post by omginternets »

ericfrederich wrote: post #10
vsmhn wrote: post #6

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…

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

aio isn't available for py2. The benefit is that this is available for py2.
Post reply on HN