chore(ci): drop support for Python 3.8

[leandrodamascena]

Issue number: #5238

Summary

Changes

On 2024-10-25, we announced the deprecation of Python 3.8 in Powertools, scheduled for 2025-02-07. During this time, we continued to release versions for Python 3.8 and allowed customers to migrate to newer versions of Python without any impact.

AWS Lambda

AWS Lambda runtime will fully deprecate Python 3.8 on Mar 31, 2025. This means, 3.8 functions will be unable to be updated. Inline with this, Powertools releases will stop supporting it.

We strongly advice you update your Lambda functions to at least Python 3.10+.

User experience

Customers will no longer be able to use Powertools for AWS Lambda (Python) with Python 3.8.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.22%. Comparing base (792892e) to head (921e058).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #5896      +/-   ##
===========================================
+ Coverage    96.20%   96.22%   +0.01%     
===========================================
  Files          232      232              
  Lines        10955    10955              
  Branches      2026      790    -1236     
===========================================
+ Hits         10539    10541       +2     
  Misses         327      327              
+ Partials        89       87       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dreamorosi]

Thanks for working on this.

Leaving a comment, but feel free to not implement it, if you think it's not useful:

The upgrade guide from v2 to v3 currently says to migrate to at least 3.8. That was true at that time, but if someone follows the guide next week they might get stuck since the version at that time doesn't support it anymore. Not sure you want to change it or call out that we dropped support.

Other than this, good to go.

[leandrodamascena]

The upgrade guide from v2 to v3 currently says to migrate to at least 3.8. That was true at that time, but if someone follows the guide next week they might get stuck since the version at that time doesn't support it anymore. Not sure you want to change it or call out that we dropped support.

You're right here and it's a good point, but I don't think we should be encouraging customers to adopt 3.8 anymore, especially since if someone is migrating from version 2 to version 3 and sticking with Python 3.8, that means they have less than 2 months to get everything done and never change a single line of code in that function again because AWS Lambda will drop update function soon.

What do you think about waiting for someone to open an issue or complain about it? Then we can provide specific answers to specific requests, that is, if they happen.

[dreamorosi]

The upgrade guide from v2 to v3 currently says to migrate to at least 3.8. That was true at that time, but if someone follows the guide next week they might get stuck since the version at that time doesn't support it anymore. Not sure you want to change it or call out that we dropped support.

You're right here and it's a good point, but I don't think we should be encouraging customers to adopt 3.8 anymore, especially since if someone is migrating from version 2 to version 3 and sticking with Python 3.8, that means they have less than 2 months to get everything done and never change a single line of code in that function again because AWS Lambda will drop update function soon.

What do you think about waiting for someone to open an issue or complain about it? Then we can provide specific answers to specific requests, that is, if they happen.

Sorry I haven't been clear maybe.

My suggestion was to update the text in the upgrade guide to say "upgrade to at least 3.9".

[leandrodamascena]

My suggestion was to update the text in the upgrade guide to say "upgrade to at least 3.9".

This: https://github.com/aws-powertools/powertools-lambda-python/pull/5896/files#diff-3ec187be4d5027db52c481841dbbf321b2f4b39dea03033c971aeba9a4a20e51R34?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dreamorosi]

Thanks for the PR and for addressing my comments.