Replace remaining examples with on_fetch with WorkerEntrypoint class (#25794)

Author: hoodmane

src/content/changelog/workflows/2025-08-22-workflows-python-beta.mdx

@@ -7,9 +7,9 @@ products:
 date: 2025-08-22
 ---
 
-import { Render, PackageManagers, TypeScriptExample } from "~/components"
+import { Render, PackageManagers, TypeScriptExample } from "~/components";
 
-You can now build [Workflows](/workflows/) using Python. With Python Workflows, you get automatic retries, state persistence, and the ability to run multi-step operations that can span minutes, hours, or weeks using Python’s familiar syntax and the [Python Workers](/workers/languages/python/) runtime. 
+You can now build [Workflows](/workflows/) using Python. With Python Workflows, you get automatic retries, state persistence, and the ability to run multi-step operations that can span minutes, hours, or weeks using Python’s familiar syntax and the [Python Workers](/workers/languages/python/) runtime.
 
 Python Workflows use the same step-based execution model as JavaScript Workflows, but with Python syntax and access to Python’s ecosystem. Python Workflows also enable [DAG (Directed Acyclic Graph) workflows](/workflows/python/dag/), where you can define complex dependencies between steps using the depends parameter.
 
@@ -36,9 +36,10 @@ class PythonWorkflowStarter(WorkflowEntrypoint):
 
         await my_second_step()
 
-async def on_fetch(request, env):
-    await env.MY_WORKFLOW.create()
-    return Response("Hello Workflow creation!")
+class Default(WorkerEntrypoint):
+    async def fetch(self, request):
+        await self.env.MY_WORKFLOW.create()
+        return Response("Hello Workflow creation!")
 ```
 
 :::note
@@ -47,4 +48,4 @@ Python Workflows requires a `compatibility_date = "2025-08-01"`, or lower, in yo
 
 Python Workflows support the same core capabilities as JavaScript Workflows, including sleep scheduling, event-driven workflows, and built-in error handling with configurable retry policies.
 
-To learn more and get started, refer to [Python Workflows documentation](/workflows/python/).
+To learn more and get started, refer to [Python Workflows documentation](/workflows/python/).

src/content/docs/workflows/python/bindings.mdx

@@ -71,14 +71,17 @@ Create (trigger) a new instance of a given Workflow.
   type.
 
 ```python
-from pyodide.ffi import to_js
 from js import Object
+from pyodide.ffi import to_js
+from workers import WorkerEntrypoint, Response
+
 
-async def on_fetch(request, env, ctx):
-    event = {"foo": "bar"}
-    options = to_js({"params": event}, dict_converter=Object.fromEntries)
-    await env.MY_WORKFLOW.create(options)
-    return Response.json({"status": "success"})
+class Default(WorkerEntrypoint):
+    async def fetch(self, request):
+        event = {"foo": "bar"}
+        options = to_js({"params": event}, dict_converter=Object.fromEntries)
+        await self.env.MY_WORKFLOW.create(options)
+        return Response.json({"status": "success"})
 ```
 
 :::note

src/content/docs/workflows/python/python-workers-api.mdx

@@ -141,13 +141,13 @@ class DemoWorkflowClass(WorkflowEntrypoint):
 
 ### Create an instance via binding
 
-Note that `env` is a Javascript object exposed to the Python script via [JsProxy](https://pyodide.org/en/stable/usage/api/python-api/ffi.html#pyodide.ffi.JsProxy). You can
-access the binding like you would on a Javascript worker. Refer to the [Workflow binding documentation](/workflows/build/workers-api/#workflow) to learn more about the methods available.
+Note that `env` is a JavaScript object exposed to the Python script via [JsProxy](https://pyodide.org/en/stable/usage/api/python-api/ffi.html#pyodide.ffi.JsProxy). You can access the binding like you would on a JavaScript worker. Refer to the [Workflow binding documentation](/workflows/build/workers-api/#workflow) to learn more about the methods available.
 
 Let's consider the previous binding called `MY_WORKFLOW`. Here's how you would create a new instance:
 
 ```python
-async def on_fetch(request, env):
-    instance = await env.MY_WORKFLOW.create()
-    return Response.json({"status": "success"})
+class Default(WorkerEntrypoint):
+    async def fetch(self, request):
+        instance = await self.env.MY_WORKFLOW.create()
+        return Response.json({"status": "success"})
 ```