We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in request():
sock = await timeout_manager( connection_timeout, self._grab_connection, url)
so this is establishing a connection, not making the request. Yet timeout_manager() will raise RequestTimeout.
Overall it would be helpful if exception cases are documented for request().
The text was updated successfully, but these errors were encountered:
Fair point. I lazily reused that for both the connection and the request, rather than give them a base class.
I'll sort this and slap it in the docs :)
Sorry, something went wrong.
This was resolved in ced7a74
I don't think so, since that commit predates the problem report by a year.
Yeah no, @belm0 was asking for two separate possible exceptions:
ConnectionTimeout on failed connection attempts. RequestTimeout on successful connects where the server didn't respond to the https request on time.
ConnectionTimeout
RequestTimeout
No branches or pull requests
in request():
so this is establishing a connection, not making the request. Yet timeout_manager() will raise RequestTimeout.
Overall it would be helpful if exception cases are documented for request().
The text was updated successfully, but these errors were encountered: