Maintenance: drop support for Python 3.8

[leandrodamascena]

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

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[leandrodamascena]

We will remove Python 3.8 in the next release of Powertools, which will be on 1/28/2025.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 3.5.0 version!