Skip to content
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.

Consider compatibility layer #3

Open
Lukasa opened this issue Jan 27, 2014 · 5 comments
Open

Consider compatibility layer #3

Lukasa opened this issue Jan 27, 2014 · 5 comments
Labels
Long-Term Goal

Comments

@Lukasa
Copy link
Member

Lukasa commented Jan 27, 2014

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.
@sigmavirus24
Copy link
Contributor

👍

@Lukasa
Copy link
Member Author

Lukasa commented Feb 10, 2014

I'm going to do this, at least for early releases.

@Lukasa Lukasa mentioned this issue Feb 16, 2014
Open
@shazow
Copy link

shazow commented Feb 16, 2014

👍 👍

@piotr-dobrogost
Copy link

👍

@Lukasa
Copy link
Member Author

Lukasa commented Apr 3, 2015

Alrighty, we're on now that HTTP/1.1 is merged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Long-Term Goal
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@shazow @piotr-dobrogost @sigmavirus24 @Lukasa