You need to install pre-commit:

pre-commit install

And then re-commit. It's failing on the linter.

Linting fixed here @RemyTinco

I successfully deployed a Django REST Framework (DRF) project on Python 3.13 using this branch of Zappa.

Installed the branch locally with pip:

python --version
Python 3.13.2

pip install ../Zappa
...
Successfully installed zappa-0.59.0

Here’s the project repo I used for testing: https://github.com/RemyTinco/drf-zappa-poc-313
It includes a simple view that returns the Python version from the deployed Lambda environment.

The app is live here: https://6fmlmc1r2g.execute-api.eu-west-2.amazonaws.com/dev/api/version/

Here’s the JSON response from the /api/version/ endpoint:

Python Version  
GET /dev/api/version/  
HTTP 200 OK  
Allow: OPTIONS, GET  
Content-Type: application/json  
Vary: Accept

{
    "python_version": "3.13.2 (main, Feb 21 2025, 10:14:07) [GCC 11.4.1 20230605 (Red Hat 11.4.1-2)]"
}

Hey @monkut, all the code changes are in and the test deployment to AWS with Python 3.13 looks good (shared above). I'm just waiting on the CI checks to start/finish.

In the meantime, happy to receive any review or thoughts on next steps whenever you have a moment!

I Can attest to Remy. I have deployed my app TallyOnWheels with Python 3.13 without any hiccups. All lamda invocation seems to be happening without any issue.

@RemyTinco

Looks like the version of django used in the testcase requires cgi which was removed in python 3.13.
Can you update the django version used in testing?

@RemyTinco

Sorry about the delays, we've had some org/project issues that recently got sorted out.
Once this passes and get's merged, I'll issue a release!

coverage: 74.824% (+0.03%) from 74.797%
when pulling 572bc8b on RemyTinco:feature/python313
into b83a1da on zappa:master.