Andrey Petrov

Yea, I agree that a full read wouldn't make sense, but a small read -> close if something is returned sounds like a reasonable thing to prototype.

In terms of volunteering to build this? Happy to if there's a bounty/funding, otherwise I'm restricting my self-funded urllib3 time to just project management/code reviews/minor fixes for the near future....

🌸

If/when the `SessionManager` layer is complete (not sure whether that's on the roadmap anymore), which might someday supersede the `PoolManager` as the default high-level entry point, it would be a...

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` (v1.x)...

Also related thread that has many good ideas, some of which we've already done: https://github.com/urllib3/urllib3/issues/776

> You basically nailed it with the polluting v1.x series with deprecation warnings. 1.x will still be supported so there's no reason users can't continue to use the features they're...

> 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...

My pet feature request: Add a default PoolManager, so that beginners don't have to be intimidated by the word "PoolManager". [Go does this also](https://github.com/golang/go/blob/7fbd8c75c6c57e713069a3a405e5cde26cfae090/src/net/http/client.go#L110), and it seems to work very...

Proposal for consideration: Add back verb shortcuts? (I don't have strong feelings about this, but something that could be worth considering for v2.) urllib3 originally launched with verb shortcuts, but...