Hi Steven, q2_requests wraps python's request library so it will have the same interface with the added benefit of logging and asynchronous call handling. Anything you have in the python request library documentation will also be applicable to q2_requests. You can set a timeout the way you normally would and expect it to behave the same way. We also provide the ability to set timeouts at the environment level (the default is 30 seconds), but I believe that would be applicable to all of your extensions  

Hi Steven, q2_requests wraps python's request library so it will have the same interface with the added benefit of logging and asynchronous call handling. Anything you have in the python request library documentation will also be applicable to q2_requests. You can set a timeout the way you normally would and expect it to behave the same way.  

Hi Steven, q2_requests wraps python's request library so it will have the same interface with the added benefit of logging and asynchronous call handling therefore anything you have in the python requests library documentation will also be applicable to q2_requests. You can set a timeout the same way you normally would with the python request library and expect it to behave the same way.  

Hi Steven, q2_requests wraps python's request library so it will have the same interface with the added benefit of logging and asynchronous call handling. Anything you have in the python request library documentation will also be applicable to q2_requests. You can set a timeout the same way you normally would and expect it to behave the same way.