Skip to content
New issue

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

Tidy up changes added with PR#115 and limit it to only work with Python3.12 in Lambda. #124

Merged
merged 6 commits into from
Oct 27, 2023

Conversation

pushkarchawda
Copy link
Contributor

Description of changes:

  • Tidy up changes added with PR#115 and limit it to only work with Pytho3.12 in Lambda.

Target (OCI, Managed Runtime, both): OCI and Managed Runtime

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

# which can then process signals.
if self.use_thread_for_polling_next:
try:
from concurrent.futures import ThreadPoolExecutor
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with keeping it here and not in constructor. Performance overhead is negligible, maybe if one day we refactor LambdaRuntimeClient() class, we will revisit the location of lazy imports
Thank you for addressing the comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants