Add complete platform for Python 3.11 in Lambda #19626
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexey-tereshenkov-aiven
approved these changes
Aug 20, 2023
AlexTereshenkov
approved these changes
Aug 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a cached complete platform JSON file for the new support for Python 3.11 in Lambda https://aws.amazon.com/blogs/compute/python-3-11-runtime-now-available-in-aws-lambda/
As a bit of a drive-by, this also updates the other files based on what seems to be upstream changes to the builder images.
As a reminder, #19253 set up this infrastructure for pre-baked complete-platform JSON files for the AWS Lambda environment, which enables Pants 2.18 to build lambdas that pick the right wheels more reliably than just approximating via the
--platform"incomplete" platform summary.