Mike Lissner

> It's extremely unclear to me what "wrong" means here. They aren't wrong: they work, as designed. I think the point that's generally acknowledged by this bug is that the...

That's fair enough, @Lukasa. What about making the Timeout section more explicit then? Right now it says: > You can tell Requests to stop waiting for a response after a...

I doubt this will change anybody's mind, but I *vehemently* disagree with closing this bug without a fix. We improved the documentation via the PR that I filed, but in...

Hooray for reopening this bug. I like the solution of providing a default with an env override. Seems simple enough to me. > You really shouldn't be hitting the internet...

I pushed for documentation updates too and I think the docs are pretty good now, but I think the overall goodness of requests creates a blind spot for developers. It's...

As the person that filed this nearly five years ago, as a long-time user of requests that doesn't have any other issues with it, as a reviewer of pull requests...

Over in #5779, there is a bit of discussion about how to fix this, but I think the blocker here is that we don't have direction on what kind of...

Thanks @sigmavirus24, that's helpful. 3.0 looks like it may never come though — it's already been in the works for at least five years and the milestone has a lot...

I'd love to help make this happen, but I'm in the same place wrt time, just different repos, I think. Sounds like if 3.0 is a far-off hope, maybe the...

Also, thank you for the detailed reply. I'm sure this is a really hard project to maintain.