-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Announcement] Deprecating AWS SAM CLI on Python3.7 on Oct 24th, 2023 #5889
Comments
jfuss
added
the
stage/needs-triage
Automatically applied to new issues and PRs, indicating they haven't been looked at.
label
Sep 5, 2023
mndeveci
removed
the
stage/needs-triage
Automatically applied to new issues and PRs, indicating they haven't been looked at.
label
Sep 6, 2023
super132
changed the title
[Announcement] Deprecating AWS SAM CLI on Python3.7 on 0ct 24th, 2023
[Announcement] Deprecating AWS SAM CLI on Python3.7 on Oct 24th, 2023
Sep 8, 2023
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NOTE: If you are installing AWS SAM CLI with Homebrew, Native Linux Installer or through MSI, you are not impacted by this change.
As of now, AWS SAM CLI can be installed or used as a library within python3.7+ versions. However, python3.7 has reached its end of life by June 26th, 2023.
What is deprecation schedule?
AWS SAM CLI will not work on python3.7 environments by October 24th, 2023.
Will this impact my AWS Lambda functions using python3.7?
No, AWS Lambda functions which is using python3.7 as runtime will not be affected by this change. For more information about supported runtimes, please check https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html
Am I impacted by this deprecation?
If you are installing AWS SAM CLI with Homebrew, Native Linux Installer or through MSI, you are not impacted by this change. Following use cases will be impacted by this change;
The text was updated successfully, but these errors were encountered: