Cloudflare's Python Workers Hit General Availability, But Maintenance and Performance Concerns Remain

Cloudflare has officially launched Python Workers as a production-ready offering, enabling developers to run Python code on its serverless platform alongside JavaScript and TypeScript. The milestone comes two years after an initial preview and includes integrations with the company's storage, database, and queue services, plus compatibility with popular frameworks like FastAPI, Django, and Flask.

Three Key Technical Breakthroughs#

The launch rested on three major engineering efforts, notably two originating outside Cloudflare itself.

Packaging standardization was the first hurdle. Python Workers execute via Pyodide, which requires any package containing C, C++, or Rust code to be recompiled into WebAssembly. Rather than continuing to compile packages in-house, Cloudflare championed PEP 783, a cross-industry specification that lets third-party maintainers produce their own wheels. The company also stabilized the underlying Pyodide build tools and contributed WebAssembly support to the widely-used cibuildwheel project.

System-level networking came next. Database drivers like aiomysql and asyncpg rely on standard POSIX socket calls, which normally fail inside a WebAssembly sandbox. Cloudflare implemented those syscalls on top of its Workers connect API, creating a transparent bridge so existing drivers work without modification—unlocking support for services like Hyperdrive without requiring driver rewrites.

HTTP client compatibility was the third piece. Cloudflare contributed changes to upstream projects including requests and httpx so they route through the JavaScript fetch API when running in WebAssembly. This enables libraries like OpenAI and LangChain to function inside Workers without custom code paths.

Upstream Maintenance Tensions#

Community reaction has exposed friction around who maintains these upstream components long-term. On Hacker News, urllib3 maintainer illia-v noted that while Cloudflare funded feature development—such as Pyodide and Emscripten support—the money went to individual contributors rather than to the maintainers stewarding those changes. This distinction matters: urllib3's Emscripten backend remains marked experimental and falls outside the project's security policy. He cited CVE-2025-50182, a redirect-handling bug that surfaced only when requests moved through the fetch API, suggesting further subtle incompatibilities may lurk due to differences between browser and traditional networking semantics.