Move ThreadPoolExecutor imports from lazy to "not as lazy". It offloads unnecessary work from actual invocations, especially the first one. Existing tests are already covering affected code paths and components
ThreadPoolExecutor is still imported as a private dependency of a LambdaRuntimeClient, not exposing the symbols imported conditionally
Fix tests - the latest runtimes have changed unittest.mock.patch behavior, when sys.stdout patching does not work as expected in certain combinations with other @patch'es in our testcases
Target (OCI, Managed Runtime, both): Both
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Description of changes:
LambdaRuntimeClient, not exposing the symbols imported conditionallyunittest.mock.patchbehavior, whensys.stdoutpatching does not work as expected in certain combinations with other@patch'es in our testcasesTarget (OCI, Managed Runtime, both): Both
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.