Requests and urllib3 exception
Requests and urllib3 exception: requests.exceptions.Timeout
As text you can copy
requests.exceptions.Timeout - Kind
- Exception
- Where you meet it
- Raised in your own program by the library
What does requests.exceptions.Timeout mean in Requests and urllib3?
The request timed out. Catching this error catches both ConnectTimeout and ReadTimeout.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
What it means in trading API work
It is the parent of the two timeouts, and they mean different things for an order request: after a connect timeout nothing was sent, after a read timeout everything may have been.
This part is this site's own explanation, written for people learning to call a trading API. It is not part of the source cited above and it describes no particular broker.
What should I do about requests.exceptions.Timeout?
Catch ConnectTimeout and ReadTimeout separately where the difference matters. Always pass a timeout: the Requests quickstart says that without one a program can hang indefinitely.
This page is an independent explanation in plain words. The definition itself is in the source it was read from, which is the authority if the two ever differ.