requests

I recently ran into this problem with the popular Python "requests" library, which doesn't have a default timeout set. That's especially annoying as their slogan is "HTTP for Humans" and that doesn't feel very human friendly. There is a longstanding issue [1] to add a default timeout, but so far that hasn't happened yet. [1]: https://github.com/psf/requests/issues/3070

I absolutely agree. According to this comment [1] they're planning to introduce it in v3. [1] https://github.com/psf/requests/issues/3070#issuecomment-328...

:shrug: I've done that quite a bit. This randomly selected popular Python library does it, too[1]. The example for `os.walk` literally has `from os.path import join, getsize`[2]. The docs seem to back this up[3]: "Remember, there is nothing wrong with using `from package import specific_submodule!` In fact, this is the recommended notation unless the importing module needs to use submodules with the same name from different packages." I haven't dealt with a lot of C++ code but I feel like I see a lot of `using namespace ...` and haven't seen much `using ...;` (which I think is more readable/acceptable) [1] https://github.com/psf/requests/blob/df918c066fa275abc2bb0c9... [2] https://docs.python.org/3/library/os.html#os.walk [3] https://docs.python.org/3/tutorial/modules.html#importing-fr...

I always wondered why it was in the requests source code. https://github.com/psf/requests/blob/9b95b4e7b4df1865b058161...

It looks like requests is now owned by PSF. https://github.com/psf/requests But IDK why requests3 wasn't transferred as well, and why issues appear to be disabled on the repo now. The docs reference a timeout arg (that appears to default to the socket default timeout) for connect and/or read https://3.python-requests.org/user/advanced/#timeouts And the tests reference a timeout argument. If that doesn't work, I wonder how much work it would be to send a PR (instead of just talking s to Ken and not contributing any code)