Python 3.10 support for serverless functions?

[aorumbayev]

Hello Vercel team and community members! 👋

Wanted to kick off this discussion to see if there is a planned roadmap for releasing support for python 3.10 in serverless function as its been around 2 years since support for 3.9 has been announced.

Regards,
Al

[swarnava]

Hi, As soon as our upstream provider make it available, we will start supporting it. Unfortunately, we don't have any concrete ETA on this.

[swarnava]

It's still not available yet https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html. Thanks!

[aorumbayev]

@swarnava i assume still pending on updates from AWS side?

[swarnava]

Unfortunately, yes

aws/aws-lambda-base-images#31
aws/aws-lambda-base-images#62

[OnurAkbas]

@swarnava, i can see PYthon 10 has been released, yet no changes made on Vercel? please uppgrade this.

[Waxime64]

python 3.10 is avalayble in AWS

[StigKorsnes]

Anytime soon perhaps. aws/aws-lambda-base-images#31

[hsoiland]

aws/aws-lambda-base-images#31 (comment) fyi images have come through

[swarnava]

We are working with Build team to support this. ETA is still unknown. But we will update you as soon as it's available here and vercel.com/changelog. Thank you for your patience!

[tomnortonjr]

Good evening. Any updates on the Python runtime version upgrade? Thanks.

[amyegan]

Thank you all for waiting. I don't have an ETA for 3.10 or 3.11 support with automatic deployments, but we do have a way forward for anyone comfortable using Vercel CLI: vercel/vercel#10648

[draew6]

@amyegan thanks for info

[adamstoffel]

@amyegan I reviewed the PR you linked to and I'm able to build python functions locally and deploy (using vercel build and vercel deploy --prebuilt).

However, I'm struggling because some libraries (in my case pydantic-core) are distributed as binaries so doing the local build causes binaries for my platform to download. I think the fact that the proper binaries for the Serverless Functions architecture are missing is causing an error like this (Runtime.ImportModuleError: Unable to import module 'vc__handler__python': No module named 'pydantic_core._pydantic_core') when deployed to Vercel.

Any tips on getting the right platform binaries during the build?

[adamstoffel]

@amyegan I'll also point out that the current implementation of ASGI in @vercel/python is incompatible with Python >=3.10. This means that frameworks like FastAPI won't work.

using Asynchronous Server Gateway Interface (ASGI)
[ERROR] TypeError: As of 3.10, the *loop* parameter was removed from Queue() since it is no longer necessary
Traceback (most recent call last):
  File "/var/task/vc__handler__python.py", line 305, in vc_handler
    response = asgi_cycle(__vc_module.app, body)
  File "/var/task/vc__handler__python.py", line 202, in __call__
    self.app_queue = asyncio.Queue(loop=loop)
  File "/var/lang/lib/python3.10/asyncio/queues.py", line 34, in __init__
    super().__init__(loop=loop)
  File "/var/lang/lib/python3.10/asyncio/mixins.py", line 17, in __init__
    raise TypeError(

[malazaysc]

Hello! any updates on 3.10 and 3.11?

[treehousekingcomic]

Oh its June again
Any updates on 3.10?

[XChikuX]

Is it really that hard to change runtimes?
It's generally a trivial matter. Why is it taking so long, especially if the underlying functions are already provided by AWS ?

At this point you should skip 3.10 and 3.11 altogether and directly deploy 3.12. It's vastly superior due to the removal of 'GIL'

[msoedov]

Any update on 3.10? 3.12 is already there

[zsiegel92]

Python 3.11 is supported by AWS Lambda.

Considering the massive popularity of Pydantic and FastAPI, which have vastly different type annotation APIs/behavior between Python 3.9 and 3.10, I think many people would greatly appreciate adoption of newer Lambda runtimes by Vercel.

I have no knowledge of how Vercel works this out, but I do wonder whether it would be possible to specify a Lambda runtime (AWS Lambda docs) in vercel.json rather than or in addition to a python_version in the Pipfile (Vercel docs).

Alternatively, rather than handling declarative config like this, perhaps "custom install commands for your API" would be the right entrypoint:

The Install Command defined in the Project Settings will be used for front-end frameworks that support Serverless Functions for APIs.

If you're using Serverless Functions defined in the natively supported api directory, a different Install Command will be used depending on the language of the Serverless Function. You cannot customize this Install Command.

Maybe Vercel can provide or expose some APIs to let users customize their Lambda usage. Or maybe controlling this is the core Vercel business model and it will never happen.

Any comments from someone knowledgeable would be greatly appreciated!

[zsiegel92]

I guess the answer is to contribute Community runtimes using the Runtime Developer Reference.

I guess unlike PHP, Rust, Deno, and Bash (!), Python's community has not to-date been enterprising enough to contribute any community runtimes!

[zsiegel92]

But per the quote in my previous comment, I guess this doesn't apply to serverless functions.

Again, any comment from Vercel about paths forward would be great.

[draew6]

Support modern python please. 3.9 feels ancient compared to 3.10 syntax.

[TheRobBrennan]

Any progress on this front? 3.9 is long in the tooth - would love to see 3.11.1 or newer

[XChikuX]

Fine. But, only 3.12 from 2024. 📦

[u8621011]

@XChikuX You mean vercel will support v3.12 from 2024?

[kirmola]

Any updates on this? @swarnava

[Flecart]

Updates?

[alex-goswag]

When will we have access to Python 3.11 and Python 3.12 runtimes on Serverless Functions?

[XChikuX]

I don't think they care bro.

[Flecart]

They should care....

[baseplate-admin]

They dont care because vercel is not known for it's python support. They offer it as a commodity service, i doubt anyone is using this feature at scale.

[dalist1]

They're cashing in on AI for now, give them a break.

[swarnava]

We are preparing for Python 3.12 and Ruby 3.3.0 soon. Stay tuned! 😄

[draew6]

Nice

[u8621011]

I cannot wait !~

[amyegan]

Our Python Runtime now supports Python 3.12 🙌

https://vercel.com/docs/deployments/build-image#runtime-support

[amyegan]

Thanks for sharing a link to the code! I see loop = asyncio.new_event_loop() there, which makes me think it's related to this Stack Overflow post: https://stackoverflow.com/questions/60312374/what-are-all-these-deprecated-loop-parameters-in-asyncio

Do you have a minimal reproducible example that I can share with the team?

[ernests]

Thank you @amyegan for quick response.
I could share ChatGPT refactored version :) but probably it would be better for some team member to have a look at this issue in wider context.
Essentially, Python has optimised asyncio and deprecated usage of loops as you already pointed out with Stackoverflow issue. Vercel is not alone with this issue as other libraries are also updating code base to handle asyncio.

[amyegan]

I wasn't able to see the error in my original test app, but just tried with a fresh copy of the Next.js FastAPI Starter template and I can see it now. Sent your report and repro steps to the team. Thanks again for sharing it!

[winglian]

@amyegan Is there a GH issue we can follow for this?

[winglian]

here's a PR to get the ball rolling on this vercel/vercel#11541