restore changes to tutorials

davidmrdavid · davidmrdavid · commit 6f40862d79ff · 2023-02-22T09:19:00.000-08:00
diff --git a/articles/azure-functions/durable/durable-functions-cloud-backup.md b/articles/azure-functions/durable/durable-functions-cloud-backup.md
@@ -86,25 +86,6 @@ After yielding from `context.task_all`, we know that all function calls have com
 
 ---
 
-# [Python (V2)](#tab/python-v2)
-
-The function uses the standard *function.json* for orchestrator functions.
-
-[!code-json[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_BackupSiteContent/function.json)]
-
-Here is the code that implements the orchestrator function:
-
-[!code-python[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_BackupSiteContent/\_\_init\_\_.py)]
-
-Notice the `yield context.task_all(tasks);` line. All the individual calls to the `E2_CopyFileToBlob` function were *not* yielded, which allows them to run in parallel. When we pass this array of tasks to `context.task_all`, we get back a task that won't complete *until all the copy operations have completed*. If you're familiar with [`asyncio.gather`](https://docs.python.org/3/library/asyncio-task.html#asyncio.gather) in Python, then this is not new to you. The difference is that these tasks could be running on multiple virtual machines concurrently, and the Durable Functions extension ensures that the end-to-end execution is resilient to process recycling.
-
-> [!NOTE]
-> Although tasks are conceptually similar to Python awaitables, orchestrator functions should use `yield` as well as the `context.task_all` and `context.task_any` APIs to manage task parallelization.
-
-After yielding from `context.task_all`, we know that all function calls have completed and have returned values back to us. Each call to `E2_CopyFileToBlob` returns the number of bytes uploaded, so we can calculate the sum total byte count by adding all the return values together.
-
----
-
 ### Helper activity functions
 
 The helper activity functions, as with other samples, are just regular functions that use the `activityTrigger` trigger binding.
@@ -137,16 +118,6 @@ And here is the implementation:
 
 [!code-python[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_GetFileList/\_\_init\_\_.py)]
 
-# [Python (V2)](#tab/python-v2)
-
-The *function.json* file for `E2_GetFileList` looks like the following:
-
-[!code-json[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_GetFileList/function.json)]
-
-And here is the implementation:
-
-[!code-python[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_GetFileList/\_\_init\_\_.py)]
-
 ---
 
 > [!NOTE]
@@ -183,16 +154,6 @@ The Python implementation uses the [Azure Storage SDK for Python](https://github
 
 [!code-python[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_CopyFileToBlob/\_\_init\_\_.py)]
 
-# [Python (V2)](#tab/python-v2)
-
-The *function.json* file for `E2_CopyFileToBlob` is similarly simple:
-
-[!code-json[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_CopyFileToBlob/function.json)]
-
-The Python implementation uses the [Azure Storage SDK for Python](https://github.com/Azure/azure-storage-python) to upload the files to Azure Blob Storage.
-
-[!code-python[Main](~/samples-durable-functions-python/samples/fan_in_fan_out/E2_CopyFileToBlob/\_\_init\_\_.py)]
-
 ---
 
 The implementation loads the file from disk and asynchronously streams the contents into a blob of the same name in the "backups" container. The return value is the number of bytes copied to storage, that is then used by the orchestrator function to compute the aggregate sum.
diff --git a/articles/azure-functions/durable/durable-functions-phone-verification.md b/articles/azure-functions/durable/durable-functions-phone-verification.md
@@ -69,19 +69,6 @@ Here is the code that implements the function:
 
 [!code-python[Main](~/samples-durable-functions-python/samples/human_interaction/E4_SmsPhoneVerification/\_\_init\_\_.py)]
 
-> [!NOTE]
-> It may not be obvious at first, but this orchestrator does not violate the [deterministic orchestration constraint](durable-functions-code-constraints.md). It is deterministic because the `currentUtcDateTime` property is used to calculate the timer expiration time, and it returns the same value on every replay at this point in the orchestrator code. This behavior is important to ensure that the same `winner` results from every repeated call to `context.df.Task.any`.
->
-> # [Python (V2)](#tab/python-v2)
-
-The **E4_SmsPhoneVerification** function uses the standard *function.json* for orchestrator functions.
-
-[!code-json[Main](~/samples-durable-functions-python/samples/human_interaction/E4_SmsPhoneVerification/function.json)]
-
-Here is the code that implements the function:
-
-[!code-python[Main](~/samples-durable-functions-python/samples/human_interaction/E4_SmsPhoneVerification/\_\_init\_\_.py)]
-
 > [!NOTE]
 > It may not be obvious at first, but this orchestrator does not violate the [deterministic orchestration constraint](durable-functions-code-constraints.md). It is deterministic because the `currentUtcDateTime` property is used to calculate the timer expiration time, and it returns the same value on every replay at this point in the orchestrator code. This behavior is important to ensure that the same `winner` results from every repeated call to `context.df.Task.any`.
 
@@ -130,17 +117,6 @@ And here is the code that generates the four-digit challenge code and sends the
 
 [!code-python[Main](~/samples-durable-functions-python/samples/human_interaction/SendSMSChallenge/\_\_init\_\_.py)]
 
-# [Python (V2)](#tab/python-v2)
-
-The *function.json* is defined as follows:
-
-[!code-json[Main](~/samples-durable-functions-python/samples/human_interaction/SendSMSChallenge/function.json)]
-
-And here is the code that generates the four-digit challenge code and sends the SMS message:
-
-[!code-python[Main](~/samples-durable-functions-python/samples/human_interaction/SendSMSChallenge/\_\_init\_\_.py)]
-
-
 ---
 
 ## Run the sample
diff --git a/articles/azure-functions/durable/durable-functions-sequence.md b/articles/azure-functions/durable/durable-functions-sequence.md
@@ -64,6 +64,10 @@ The `context` object contains a `df` durable orchestration context object that l
 
 # [Python](#tab/python)
 
+> [!NOTE]
+> Python Durable Functions are available for the Functions 3.0 runtime only.
+
+
 #### function.json
 
 If you use Visual Studio Code or the Azure portal for development, here's the content of the *function.json* file for the orchestrator function. Most orchestrator *function.json* files look almost exactly like this.
@@ -88,28 +92,6 @@ All Python orchestration functions must include the [`durable-functions` package
 
 The `context` object lets you call other *activity* functions and pass input parameters using its `call_activity` method. The code calls `E1_SayHello` three times in sequence with different parameter values, using `yield` to indicate the execution should wait on the async activity function calls to be returned. The return value of each call is returned at the end of the function.
 
-# [Python (V2)](#tab/python-v2)
-
-#### function.json
-
-[!code-json[Main](~/samples-durable-functions-python/samples-v2/function_app.py)]
-
-> [!WARNING]
-> To abide by the "no I/O" rule of orchestrator functions, don't use any input or output bindings when using the `orchestrationTrigger` trigger binding.  If other input or output bindings are needed, they should instead be used in the context of `activityTrigger` functions, which are called by the orchestrator. For more information, see the [orchestrator function code constraints](durable-functions-code-constraints.md) article.
-
-#### \_\_init\_\_.py
-
-Here is the orchestrator function:
-
-[!code-python[Main](~/samples-durable-functions-python/samples-v2/function_chaining/function_app.py)]
-
-All Python orchestration functions must include the [`durable-functions` package](https://pypi.org/project/azure-functions-durable). It's a library that enables you to write Durable Functions in Python. There are two significant differences between an orchestrator function and other Python functions:
-
-1. The orchestrator function is a [generator function](https://wiki.python.org/moin/Generators).
-2. The _file_ should register the orchestrator function as an orchestrator by stating `main = df.Orchestrator.create(<orchestrator function name>)` at the end of the file. This helps distinguish it from other, helper, functions declared in the file.
-
-The `context` object lets you call other *activity* functions and pass input parameters using its `call_activity` method. The code calls `E1_SayHello` three times in sequence with different parameter values, using `yield` to indicate the execution should wait on the async activity function calls to be returned. The return value of each call is returned at the end of the function.
-
 ---
 
 ## E1_SayHello activity function
@@ -164,25 +146,6 @@ The implementation of `E1_SayHello` is a relatively trivial string formatting op
 
 Unlike the orchestrator function, an activity function needs no special setup. The input passed to it by the orchestrator function is directly accessible as the parameter to the function.
 
-# [Python (V2)](#tab/python-v2)
-
-#### E1_SayHello/function.json
-
-The *function.json* file for the activity function `E1_SayHello` is similar to that of `E1_HelloSequence` except that it uses an `activityTrigger` binding type instead of an `orchestrationTrigger` binding type.
-
-[!code-json[Main](~/samples-durable-functions-python/samples/function_chaining/E1_SayHello/function.json)]
-
-> [!NOTE]
-> All activity functions called by an orchestration function must use the `activityTrigger` binding.
-
-The implementation of `E1_SayHello` is a relatively trivial string formatting operation.
-
-#### E1_SayHello/\_\_init\_\_.py
-
-[!code-python[Main](~/samples-durable-functions-python/samples/function_chaining/E1_SayHello/\_\_init\_\_.py)]
-
-Unlike the orchestrator function, an activity function needs no special setup. The input passed to it by the orchestrator function is directly accessible as the parameter to the function.
-
 ---
 
 ## HttpStart client function
@@ -223,20 +186,6 @@ To interact with orchestrators, the function must include a `durableClient` inpu
 
 Use the `DurableOrchestrationClient` constructor to obtain a Durable Functions client. You use the client to start an orchestration. It can also help you return an HTTP response containing URLs for checking the status of the new orchestration.
 
-# [Python (V2)](#tab/python-v2)
-
-#### HttpStart/function.json
-
-[!code-json[Main](~/samples-durable-functions-python/samples/function_chaining/HttpStart/function.json)]
-
-To interact with orchestrators, the function must include a `durableClient` input binding.
-
-#### HttpStart/\_\_init\_\_.py
-
-[!code-python[Main](~/samples-durable-functions-python/samples/function_chaining/HttpStart/\_\_init\_\_.py)]
-
-Use the `DurableOrchestrationClient` constructor to obtain a Durable Functions client. You use the client to start an orchestration. It can also help you return an HTTP response containing URLs for checking the status of the new orchestration.
-
 ---
 
 ## Run the sample
