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

Maintenance: drop support for Python 3.8 #5238

Open
1 of 2 tasks
leandrodamascena opened this issue Sep 25, 2024 · 0 comments
Open
1 of 2 tasks

Maintenance: drop support for Python 3.8 #5238

leandrodamascena opened this issue Sep 25, 2024 · 0 comments
Assignees
Labels
internal Maintenance changes

Comments

@leandrodamascena
Copy link
Contributor

Why is this needed?

Summary

Important

Starting from February 7, 2025 Powertools for AWS Lambda (Python) will end support for Python 3.8

This action follows the date when AWS Lambda will mark the python3.8 as deprecated and precedes the date after which you will no longer be able to create new functions using the runtime.

We recommend that you upgrade your existing Python 3.8 functions to Python 3.10+ before February 7, 2025.

End of support does not impact existing functions and functions using versions of Powertools for AWS Lambda (Python) released before the date, however starting from this date we will not guarantee compatibility with Python 3.8.

You can use the following AWS CLI command to list all functions in a specific region using Python 3.8, including published function versions:

Note

Make sure to replace the value of the --region flag and run this command in each region you have Lambda functions workloads

aws lambda list-functions --function-version ALL --region <Region> --output text --query "Functions[?Runtime=='python3.8'].FunctionArn"

Why is this needed?

Starting from Feb 28, 2025 we will no longer be able to deploy new Lambda functions using the python3.8 runtime, this means we will no longer be able to run integration tests for new code changes.

With this in mind, we plan on dropping support for the runtime just three weeks before the date to avoid any impact in our releases and end2end tests.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

@leandrodamascena leandrodamascena added triage Pending triage from maintainers internal Maintenance changes labels Sep 25, 2024
@leandrodamascena leandrodamascena removed the triage Pending triage from maintainers label Sep 25, 2024
@leandrodamascena leandrodamascena self-assigned this Sep 25, 2024
@leandrodamascena leandrodamascena pinned this issue Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Maintenance changes
Projects
Status: Backlog
Development

No branches or pull requests

1 participant