Cloudflare has released Python Workers to general availability, two years after its initial preview, allowing developers to run Python alongside JavaScript and TypeScript on its edge computing platform. The launch includes connections to Workers AI, R2, D1, Hyperdrive, Durable Objects, Queues and Workflows, plus support for FastAPI, Django and Flask frameworks. But the release has sparked divided reactions, with critics questioning cold start performance and the company's approach to funding open source maintainers.
Three engineering achievements made the launch possible, according to Cloudflare's announcement. The first is a packaging standard: Python Workers operate on Pyodide, requiring packages with C, C++, or Rust extensions to be cross-compiled to WebAssembly. Cloudflare proposed PEP 783, which standardizes a platform called PyEmscripten for Python in browser runtimes, and it was accepted after more than a year. The second is a socket bridge that implements POSIX system calls over the Workers connect API, allowing drivers like aiomysql and asyncpg to function without modifications inside a WebAssembly sandbox. The third involves upstream contributions to HTTP clients including requests and httpx, which now route through the JavaScript fetch API in WebAssembly environments, enabling OpenAI, LangChain, and MCP to run inside a Worker.
The urllib3 maintainer illia-v raised concerns about the funding model, writing on Hacker News that while his project merged substantial contributions adding Pyodide and Emscripten support, "There is a meaningful difference between funding a contribution to an upstream project and funding the upstream maintainers." He noted the Emscripten backend remains experimental in urllib3 and is explicitly excluded from the project's security policy, pointing to CVE-2025-50182 where urllib3's redirect controls didn't behave as expected once requests were routed through fetch. Syrus Akbary, founder of competing platform Wasmer, questioned cold start performance, stating a minimal Python application started in around 60ms on Wasmer Edge versus roughly 900ms on Cloudflare Workers in a benchmark published earlier this year. Dominik Picheta from Cloudflare responded that their memory snapshot implementation has improved cold starts significantly, and sharding reduces how often they occur.
The community debate highlights tensions around how WebAssembly-based Python execution performs compared to native implementations. The socket bridge works because the translation happens at the syscall level, meaning existing database drivers require no code changes to function on the platform. The HTTP client routing through fetch creates potential security differences, however, because browser networking semantics diverge from urllib3's typical backend behavior. Hood Chatham, a Pyodide contributor Cloudflare hired, explained that using the JavaScript event loop is necessary because that's where I/O events occur in the runtime, and a second loop would block them. Version coupling emerged as another concern, with developers tied to the Python and Pyodide version embedded in workerd, though compatibility flags now select between Python 3.12, 3.13 and 3.14.
Cloudflare has published production patterns in a python-workers-examples repository, and its developer documentation now displays Python alongside JavaScript and TypeScript across products. On performance, the company states only that it plans to make Python Workers more performant and memory-efficient, without providing current p50 and p95 startup figures or addressing memory allocation concerns that one commenter estimated could consume tens of megabytes per worker. The packaging standard removes dependency on a single vendor compiling wheels, and two of the three authors on the announcement maintain Pyodide itself, the project the runtime depends on. The decision to route Python networking through browser APIs rather than traditional sockets represents a calculated trade-off between edge deployment speed and compatibility guarantees that enterprises typically expect from production infrastructure.