This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: HTTP/2.0 - Implementations/Testing efforts
Type: Stage:
Components: Library (Lib) Versions: Python 3.4
process
Status: closed Resolution: postponed
Dependencies: Superseder:
Assigned To: Nosy List: christian.heimes, karlcow, orsenthil, pitrou
Priority: normal Keywords:

Created on 2013-02-26 20:54 by karlcow, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (6)
msg183086 - (view) Author: karl (karlcow) * Date: 2013-02-26 20:54
Are there plans to develop an HTTP/2.0 library in parallel of the specification development? It will not be ready before years, but it would be good to have an evolving implementation. Or should it be done outside of python.org?

Reference: https://github.com/http2
msg183088 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2013-02-26 20:57
It should certainly be done outside of python.org.
Also, I think the stdlib already lacks some HTTP/1.1 features, better start there...
msg183089 - (view) Author: Senthil Kumaran (orsenthil) * (Python committer) Date: 2013-02-26 21:20
Yes, feature complete of 1.1 will be a start. :(
msg183097 - (view) Author: karl (karlcow) * Date: 2013-02-26 22:19
agreed on HTTP/1.1, is there a plan to fix it too ;) because the current http.server seems to be untouchable without breaking stuff all around :)
msg183135 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2013-02-27 11:03
> agreed on HTTP/1.1, is there a plan to fix it too ;) because the
> current http.server seems to be untouchable without breaking stuff
> all around :)

The way to do it without breaking compatibility would be to write a new
handler, see my platonic proposal at
http://mail.python.org/pipermail/python-dev/2012-September/121806.html
msg183141 - (view) Author: karl (karlcow) * Date: 2013-02-27 11:51
Read the thread. Thanks Antoine. Better understanding. I'm still discovering how the community is really working.

Trying to fix a few things in the mean time 

http://bugs.python.org/issue12921
http://bugs.python.org/issue747320
http://bugs.python.org/issue11448
http://bugs.python.org/issue7370 (maybe this one is a duplicate of 747320)

This one 
http://bugs.python.org/issue15799
which is still "open", make me thinks, that it might in the new class to have things for strict production rules, and some parsing rules with a warning mode, if the user cares.

Thanks again for the context Antoine. Maybe we should close this bug as postponed?
History
Date User Action Args
2022-04-11 14:57:42adminsetgithub: 61504
2013-03-01 21:00:43terry.reedysetstatus: open -> closed
resolution: postponed
2013-02-27 11:57:14christian.heimessetnosy: + christian.heimes
2013-02-27 11:51:51karlcowsetmessages: + msg183141
2013-02-27 11:03:48pitrousetmessages: + msg183135
2013-02-26 22:19:19karlcowsetmessages: + msg183097
2013-02-26 21:20:19orsenthilsetnosy: + orsenthil
messages: + msg183089
2013-02-26 20:57:09pitrousetnosy: + pitrou
messages: + msg183088
2013-02-26 20:54:45karlcowcreate