The Future of Python HTTP

Re:The Future of Python HTTP by sho_hn on Monday April 02, 2012 @02:36AM (#3786609)

What about Python 3? Other than the async submodule (due to the missing gevent dep), requests already supports Python 3, but Werkzeug does not. Is part of the plan for the combined effort to change this, or will requests lose Python 3 support again? (This seems unlikely, but I thought I better ask.)

[ Parent | on HN ]

Re:The Future of Python HTTP by kenneth_reitz on Monday April 02, 2012 @02:40AM (#3786622)

All of these changes are targeted at Python 2.6–3.x.

A rewrite of many parts of Werkzeug is required to support Python 3. Might as well kill two birds with one stone :)

[ Parent | on HN ]

Re:The Future of Python HTTP by sho_hn on Monday April 02, 2012 @02:56AM (#3786654)

Sounds good. Thanks!

Edit: As a bonus link to make this post more interesting, the other day I caused the Python 3 version of requests to be packaged for Fedora 16 and 17: https://bugzilla.redhat.com/show_bug.cgi?id=807525

[ Parent | on HN ]

Re:The Future of Python HTTP by kenneth_reitz on Monday April 02, 2012 @03:08AM (#3786687)

Awesome, thanks the help! I really appreciate it :)

[ Parent | on HN ]