Support for Python 3.13 Lambdas

Open

#278 opened on Aug 28, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 45/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: aws, python
Domain: cloud

Research direction

Start by locating the plugin's AWS Lambda runtime validation or resource deployment path and reproduce the reported Python 3.13 deployment failure. Done means a configuration using python3.13 is accepted and its Lambda deploys successfully against LocalStack.

Written by the indexing model from the issue text.

Description

Context

AWS announced support for Python 3.13 runtime in November 2024. When attempting to deploy to Localstack, however, I get the following error:

      StackId: 'arn:aws:cloudformation:***:000000000000:stack/proj/00000',
      EventId: '137610ba-70c5-44f1-89a1-2a906c535d2d',
      StackName: 'business-analytics-serverless-local',
      LogicalResourceId: 'MyLambdaFunction',
      PhysicalResourceId: 'arn:aws:cloudformation:***:000000000000:stack/proj/00000',
      ResourceType: 'AWS::Lambda::Function',
      Timestamp: 2025-08-28T13:53:58.640Z,
      ResourceStatus: 'CREATE_FAILED',
      ResourceStatusReason: "An error occurred (InvalidParameterValueException) when calling the CreateFunction operation: Value python3.13 at 'runtime' failed to satisfy constraint: Member must satisfy enum value set: [nodejs20.x, provided.al2023, python3.12, java17, nodejs16.x, dotnet8, python3.10, java11, python3.11, dotnet6, java21, nodejs18.x, provided.al2, ruby3.3, java8.al2, ruby3.2, python3.8, python3.9] or be a valid ARN"

Expected Behavior

Successful deployment of Python 3.13 Lambdas.

Dominant language: JavaScript
Stars: 542
Forks: 92
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[BUG] @mastra/inngest: errors thrown inside durable steps lose their original stack (and error type) — Inngest only sees the wrapper frame Open

bug customer-eng Durable Agents Inngest status: needs triage

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

mastra-ai/mastra#24748 · 1 comment · Opened Sep 22, 2026
[optimization:agents-md-curator] Trim and correct root ambient context in github/gh-aw-firewall (LOGGING.md dead link, stale test claim, ~12% context reduction) Open

optimization optimization:agents-md-curator

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

githubnext/gh-aw-cao#13475 · Opened Sep 22, 2026
[BUG]: "Clear All" in Settings doesn't clear the saved analysis, old data comes back after reload Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

AOSSIE-Org/OrgExplorer#253 · 1 comment · Opened Sep 22, 2026
isolated-declarations: TS9025 on an optional parameter property typed `readonly T[]`, which tsc 7 accepts Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

oxc-project/oxc#26944 · Opened Sep 22, 2026
bug report: ai observability - dry-running a paused evaluation emails the whole org Open

ai-observability bug team/ai-observability

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

PostHog/posthog#104687 · Opened Sep 22, 2026

More JavaScript issues