Cloudflare's Python Workers are now available to all users

If you're a Python developer curious about running your code on Cloudflare's edge platform, there's good news: Python Workers are officially stable and ready for production use. After two years in preview, Cloudflare has confirmed that "Python is now a first-class, fully supported language on the Cloudflare Developer Platform." Here's what that means, how the technology actually works under the hood, and where the rough edges still are.

From preview to production

Cloudflare first teased Python support in its Workers platform two years ago, and the feature has spent that entire time in an extended preview phase. Now the company considers it fully supported, which signals that the APIs and behavior developers can rely on going forward are settled. For teams that were hesitant to build on an experimental feature, this announcement removes a major reason for caution.

The release announcement credits Gyeongjae Choi, Dominik Picheta, and Hood Chatham. Notably, both Choi and Chatham are core maintainers of Pyodide, which hints at just how central that project is to making all of this work.

How Python actually runs on Workers

The most interesting part of this story is the engineering approach. Cloudflare didn't build a Python interpreter from scratch or bolt a new runtime onto their platform. Instead, they compile Python to WebAssembly using Pyodide, then run that inside workerd, their V8-based JavaScript runtime.

In other words, your Python code executes within the same browser-grade WebAssembly machinery that powers V8 itself. It's a pragmatic solution that lets Cloudflare reuse existing infrastructure rather than maintain a separate Python runtime alongside their JavaScript one.

The limitations worth knowing about

This approach does come with trade-offs, and Cloudflare documents them openly. The biggest one: multiprocessing and threading simply don't work inside the WebAssembly VM. If your Python application leans heavily on parallelism, you'll need to rethink that architecture before moving it to Workers.

That said, plenty of common server-side workloads—handling HTTP requests, calling APIs, processing JSON—don't depend on threads at all. For those use cases, the platform should feel fairly natural.

Local development gets interesting

One detail that stood out is how the local development experience works. Cloudflare's development tool, called pywrangler (though it's confusingly packaged as `workers-py` on PyPI—a naming inconsistency worth knowing about), doesn't just approximate the platform locally.

Instead, it runs a full simulation of Cloudflare's actual stack on your machine. That means executing your code with Pyodide in WebAssembly inside V8, all bundled up in a 123MB workerd binary. On a Mac with Apple silicon, for example, the binary lands at `node_modules/@cloudflare/workerd-darwin-arm64/bin/workerd`.

The practical benefit here is that what runs on your laptop is essentially the same environment that runs in production. Fewer "works locally, breaks in deployment" surprises—which is a persistent pain point in serverless development generally.

A meaningful bet on Python

Beyond the technical details, this release represents a real investment by Cloudflare in the broader Python ecosystem. Recruiting Pyodide core maintainers to work on the platform suggests Cloudflare is committed to making Python genuinely well-supported, not just a checkbox feature.

For the Python community, it also opens up another deployment option: a globally distributed, serverless environment where Python is treated as an equal alongside JavaScript.

Source: Hacker News

Suggested meta description: Cloudflare Python Workers are now generally available. Learn how Pyodide and WebAssembly power them, plus key limits and local dev details.

Tags: python, cloudflare, webassembly, pyodide

Featured image: Abstract, friendly illustration of Python code flowing through a cloud-shaped edge network node, rendered in soft gradients—no people, logos, or text.