Giters

python-hyper / hyper

HTTP/2 for Python.

Home Page:http://hyper.rtfd.org/en/latest/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Is hyper still "a very early alpha"?

simonw opened this issue · comments

commented

The readme has said "Please be warned: hyper is in a very early alpha. You will encounter bugs when using it. In addition, there are very many rough edges. With that said, please try it out in your applications: I need your feedback to fix the bugs and file down the rough edges" for over six months now, but there has been a lot of active development on the project. Is that statement still accurate? If not, I suggest changing it to encourage more people to consider using it for production projects.

commented

Ping!

commented

Hi @simonw and @dimaqq,

Please be patient. @Lukasa is on vacation right now and won't be back for a few more days. There's no need to ping those watching this repository since you will get an answer shortly.

commented

@simonw Sorry about the absence. I wish GitHub had a way to set away messages. =(

This is a tricky question, mostly because I have very complex feelings towards this library. It's definitely not an early alpha any more, but I'm not sure that people will get much joy out of using it in production: it has enough problems around concurrent use cases that I think it needs to be substantially refactored and, frankly, probably has to start spawning its own threads.

Unfortunately, I don't really have the time to invest in getting this library into the state it needs to be, because I've moved a bit far down the stack of HTTP/2 to write more general solutions to the HTTP/2 problem.

Anyway, that's my gripe over. I think the TL;DR is that I think we can remove that banner and let the version number speak for itself. Want to make a PR to do that?