Andrey Petrov

How would we change it? Our options are: 1. Continue overriding 2. Raise an exception 3. Parse the header and use the provided boundary, if any (assuming the rest is...

It should be overriding, otherwise I'm pretty sure none of this will work? I believe it happens in our fields encoding step.

Huh right you are, that looks like a bug, and we need a test! :D

Any other ideas/requests? @Lukasa @sigmavirus24 @dstufft @jonparrott @t-8ch @kevinburke (feel free to cc others for feedback) Is there any big change that would make HTTP/2 support easier?

> How about, if we're going really "pie in the sky", I add: asynchronous by default? ;) I'll add to the long-shot list. Any ideas on what would need to...

@ml31415 There is tons of code in urllib3 working around httplib's shortcomings, things like unmangling headers and bugs in the state machine and others. Especially differences in the py2 vs...

Right, this would be a higher-level frontend for the other lower-level components. Maybe feature a kind of registry that external plugins can provide additional services for.

> That said, a very basic hyper-h2-alike for HTTP/1.1 shouldn't be that hard to write if we just want to spike it out and see how it looks. +1, I...

@sigmavirus24 How come? If we're going to switch out to our own http/1.1 parser, adding 1.0 and 0.9 support should be relatively easy in comparison (largely a subset with minor...

@ml31415 +0 to migrating to pytest, though I don't think we need to wait for 2.0 for this. It's not user-facing so it could be done at any point.