hyper
hyper copied to clipboard
Consider compatibility layer
It's been suggested that the compatibility layer might be a bad idea as a primary API, and instead worth moving to a separate location from which it can be imported (e.g. from hyper import httplib_compat as httplib. This would allow me to have a sensible API as the primary layer.
:+1:
I'm going to do this, at least for early releases.
:+1: :+1:
:+1:
Alrighty, we're on now that HTTP/1.1 is merged.