Fix MRO errors for TimeoutError under py311

[ymilki]

Bug

In py3.11, concurrent.futures.TimeoutError is aliased to TimeoutError. This is a problem for bravado.http_future._raise_error which constructs a dynamic error to combine the Bravado specific error with the original error. With TimeoutError and BravadoTimeoutError, this will now throw an MRO error:

E       TypeError: Cannot create a consistent method resolution
E       order (MRO) for bases TimeoutError, BravadoTimeoutError

This issue occurs with bravado-asyncio which explicitly throws concurrent.futures.TimeoutError.

Solution

_raise_error was created for python2 to ensure the original exception was not lost. With python 3, we can directly throw BravadoTimeoutError without losing the original exception.

Checking for the specific case where the caught exception is TimeoutError, we will raise BravadoTimeoutError

TODO: Drop py2. This test will fail under py2 because TimeoutError doesn't exist until py33.

Validation

bravady-asyncio has tests that will fail under py311: tests/integration/bravado_integration_test.py::TestServerBravadoAsyncioClient. This PR will make those tests pass.

TODO: Write similar tests in this repo.

[Copilot]

Pull Request Overview

This PR fixes an MRO error that arises in Python 3.11 when a TimeoutError is raised by explicitly checking for it in the _raise_timeout_error method and then raising BravadoTimeoutError.

• Adds an explicit check for TimeoutError in _raise_timeout_error
• Raises BravadoTimeoutError directly when the caught exception is a TimeoutError