Add support for Python 3.13 in templates, CI, and codebase #1364
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eviltwin
reviewed
Mar 17, 2025
| @@ -986,7 +986,7 @@ to change Zappa's behavior. Use these at your own risk! | |||
| "role_name": "MyLambdaRole", // Name of Zappa execution role. Default <project_name>-<env>-ZappaExecutionRole. To use a different, pre-existing policy, you must also set manage_roles to false. | |||
| "role_arn": "arn:aws:iam::12345:role/app-ZappaLambdaExecutionRole", // ARN of Zappa execution role. Default to None. To use a different, pre-existing policy, you must also set manage_roles to false. This overrides role_name. Use with temporary credentials via GetFederationToken. | |||
| "route53_enabled": true, // Have Zappa update your Route53 Hosted Zones when certifying with a custom domain. Default true. | |||
| "runtime": "python3.12", // Python runtime to use on Lambda. Can be one of: "python3.8", "python3.9", "python3.10", "python3.11", or "python3.12". Defaults to whatever the current Python being used is. | |||
| "runtime": "python3.12", // Python runtime to use on Lambda. Can be one of: "python3.8", "python3.9", "python3.10", "python3.11", "python3.12", or "python3.13". Defaults to whatever the current Python being used is. | |||
There was a problem hiding this comment.
Might be worth changing the sample value here to "python3.13", to keep it at the latest?
Suggested change
| "runtime": "python3.12", // Python runtime to use on Lambda. Can be one of: "python3.8", "python3.9", "python3.10", "python3.11", "python3.12", or "python3.13". Defaults to whatever the current Python being used is. | |
| "runtime": "python3.13", // Python runtime to use on Lambda. Can be one of: "python3.8", "python3.9", "python3.10", "python3.11", "python3.12", or "python3.13". Defaults to whatever the current Python being used is. |
|
You need to install And then re-commit. It's failing on the linter. |
|
Linting fixed here @RemyTinco |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for Python 3.13 in Zappa, enabling deployments on AWS Lambda with the latest Python runtime.
The following updates have been made:
SUPPORTED_VERSIONSinzappa/__init__.pyto include Python 3.13.get_runtime_from_python_version()inzappa/utilities.py..github/workflows/ci.yml) to test against Python 3.13.setup.pyclassifiers to reflect Python 3.13 support.README.mdand issue templates to mention Python 3.13 compatibility.tests/tests.pyfor verifying Python 3.13 runtime compatibility.Testing
This PR was tested by:
🟧 Running CI tests across supported Python versions (3.8 – 3.13).
🟥 Deploying a test Zappa application with Python 3.13 to AWS Lambda.
🟩 : Running unit tests to verify manylinux wheel compatibility with Python 3.13.
GitHub Issue Reference
Closes #1363