-
Notifications
You must be signed in to change notification settings - Fork 411
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
chore(ci): drop support for Python 3.7 #3638
chore(ci): drop support for Python 3.7 #3638
Conversation
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #3638 +/- ##
===========================================
+ Coverage 95.50% 96.38% +0.87%
===========================================
Files 215 214 -1
Lines 10140 10030 -110
Branches 1867 1846 -21
===========================================
- Hits 9684 9667 -17
+ Misses 343 259 -84
+ Partials 113 104 -9 ☔ View full report in Codecov by Sentry. |
On On 4, could you add the botocore version (before/after) for completeness? Just in case.. are there any > grep -i "# maintenance" -R aws_lambda_powertools/ -R tests | grep "3.7"
aws_lambda_powertools//logging/logger.py: # Maintenance: We can drop this upon Py3.7 EOL. It's a backport for "location" key to work
aws_lambda_powertools//logging/logger.py: # Maintenance: We can drop this upon Py3.7 EOL. It's a backport for "location" key to work
aws_lambda_powertools//logging/logger.py: # Maintenance: We can drop this upon Py3.7 EOL. It's a backport for "location" key to work
aws_lambda_powertools//logging/logger.py: # Maintenance: We can drop this upon Py3.7 EOL. It's a backport for "location" key to work
aws_lambda_powertools//logging/logger.py: # Maintenance: We can drop this upon Py3.7 EOL. It's a backport for "location" key to work
aws_lambda_powertools//logging/logger.py: # Maintenance: We can drop this upon Py3.7 EOL. It's a backport for "location" key to work
aws_lambda_powertools//logging/logger.py: # Maintenance: We can drop this upon Py3.7 EOL. It's a backport for "location" key
tests/e2e/idempotency_redis/conftest.py: # MAINTENANCE: Add the Stack constructor when Python 3.7 is dropped |
There are many files where we import from
Adding now.
I've already removed them all, you're probably running this grep on a branch other than this one, right? Thanks |
Yeah different branch, it was just for illustration ;-) Will review as soon as I have a break in a customer meeting |
examples/event_handler_graphql/src/assert_async_graphql_response_module.py
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one tiny suggestion to add a comment, and one question as I suspect docs code highlighting will be impacted with the change.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SHIIIIIPP IT! :) great work as always @leandrodamascena
* develop: (21 commits) chore: cleanup, add test for single and nested fix(parameters): make cache aware of single vs multiple calls docs: Add nathan hanks post community (aws-powertools#3727) chore(deps-dev): bump isort from 5.11.5 to 5.13.2 (aws-powertools#3723) chore(deps-dev): bump cfn-lint from 0.83.8 to 0.85.0 (aws-powertools#3724) chore(deps): bump actions/download-artifact from 4.1.1 to 4.1.2 (aws-powertools#3725) chore(deps-dev): bump types-python-dateutil from 2.8.19.14 to 2.8.19.20240106 (aws-powertools#3720) chore(ci): enable Redis e2e tests (aws-powertools#3718) chore(deps-dev): bump pytest from 7.4.4 to 8.0.0 (aws-powertools#3711) chore(deps): bump actions/upload-artifact from 3.1.3 to 4.3.1 (aws-powertools#3714) chore(ci): changelog rebuild (aws-powertools#3715) chore(deps-dev): bump mypy from 1.4.1 to 1.8.0 (aws-powertools#3710) chore(deps-dev): bump httpx from 0.24.1 to 0.26.0 (aws-powertools#3712) chore(deps): bump actions/download-artifact from 3.0.2 to 4.1.1 (aws-powertools#3612) chore(deps): bump codecov/codecov-action from 3.1.6 to 4.0.1 (aws-powertools#3700) chore(deps-dev): bump coverage from 7.2.7 to 7.4.1 (aws-powertools#3713) chore(deps-dev): bump the boto-typing group with 7 updates (aws-powertools#3709) chore(deps): bump squidfunk/mkdocs-material from `a4a2029` to `e0d6c67` in /docs (aws-powertools#3708) chore(deps): bump release-drafter/release-drafter from 5.25.0 to 6.0.0 (aws-powertools#3699) chore(ci): drop support for Python 3.7 (aws-powertools#3638) ...
Issue number: #3637
PLEASE DO NOT MERGE BEFORE February 8th
Summary
Changes
AWS Lambda runtime will fully deprecate Python 3.7 on February 8th. This means, 3.7 functions will be unable to be updated. Inline with this, Powertools releases will stop supporting it.
User experience
Customers will no longer be able to use Powertools for AWS Lambda (Python) with Python 3.7.
Improvements
In this pull request, we've made some enhancements, taking into account the removal of Python 3.7 support.
typing
new types added in Python 3.8 and previously only available in thetyping_extensions
library.cached_property
decorator.botocore
.Before
After
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
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.