Seth Michael Larson
Seth Michael Larson
@josephholsten contacted me about getting a solution to this and being willing to provide a patch. I'm on board for having the functionality. It'd be nice to have a shuffle...
@sigmavirus24 Mostly that if we already have a tunnel all the way down to that level of the library we could potentially reuse that tunnel since the shuffling of DNS...
Thanks for opening this. Could you point to where you're looking at in your CI to make the determination about the amount of tuples being used?
The `**pool.headers` construction interests me, maybe we can document that? Does that work with `HTTPHeaderDict`?
I created PR #1484 to potentially fix this issue.
Great catch, the iteration behavior is new and hasn't been flexed enough. Would you be willing to submit a patch to fix this issue?
I'm actually okay with having this added to the library due to it's small surface. Not sure who'd use it but I'm sure urllib3 purists may have some interest.
+1 to only implementing Connection and ConnectionPool, allows us to skip the URI handling for paths until later (if ever).
> What's the reasoning for starting deprecation warnings in `v2.0.0` (a super-major version bump) and doing actual breaking changes in `v2.1.0` rather than do deprecation warnings leading up to `v2.0.0`...
@shazow If we go that route we're splitting up the actual features with the logic for detecting when they'd be used and should emit a deprecation warning. Best to keep...