Adds Develop with Python Documentation

docs/dev-guide/golang/foundations.mdx

@@ -507,7 +507,7 @@ And the total size of a gRPC message, which includes all the arguments, is limit
 Also, keep in mind that all Payload data is recorded in the [Workflow Execution Event History](/workflows#event-history) and large Event Histories can affect Worker performance.
 This is because the entire Event History could be transferred to a Worker Process with a [Workflow Task](/workers#workflow-task).
 
-{/*TODO link to gRPC limit section when available */}
+{/* TODO link to gRPC limit section when available */}
 
 Some SDKs require that you pass context objects, others do not.
 When it comes to your application data—that is, data that is serialized and encoded into a Payload—we recommend that you use a single object as an argument that wraps the application data passed to Activities.

docs/dev-guide/javalang/durable-execution.mdx

@@ -274,7 +274,7 @@ The most important thing to take away from the section is to make sure you have
 
 Versioning APIs and versioning strategies are covered in other parts of the developer's guide, this chapter sets the stage to understand why and how to approach those strategies.
 
-{/*TODO ^ update with links to those places */}
+{/* TODO ^ update with links to those places */}
 
 ### The Event History
 

docs/dev-guide/javalang/foundations.mdx

@@ -484,7 +484,7 @@ And the total size of a gRPC message, which includes all the arguments, is limit
 Also, keep in mind that all Payload data is recorded in the [Workflow Execution Event History](/workflows#event-history) and large Event Histories can affect Worker performance.
 This is because the entire Event History could be transferred to a Worker Process with a [Workflow Task](/workers#workflow-task).
 
-{/*TODO link to gRPC limit section when available */}
+{/* TODO link to gRPC limit section when available */}
 
 Some SDKs require that you pass context objects, others do not.
 When it comes to your application data—that is, data that is serialized and encoded into a Payload—we recommend that you use a single object as an argument that wraps the application data passed to Activities.

docs/dev-guide/phplang/foundations.mdx

@@ -445,7 +445,7 @@ And the total size of a gRPC message, which includes all the arguments, is limit
 Also, keep in mind that all Payload data is recorded in the [Workflow Execution Event History](/workflows#event-history) and large Event Histories can affect Worker performance.
 This is because the entire Event History could be transferred to a Worker Process with a [Workflow Task](/workers#workflow-task).
 
-{/*TODO link to gRPC limit section when available */}
+{/* TODO link to gRPC limit section when available */}
 
 Some SDKs require that you pass context objects, others do not.
 When it comes to your application data—that is, data that is serialized and encoded into a Payload—we recommend that you use a single object as an argument that wraps the application data passed to Activities.

docs/dev-guide/tscript/features.mdx

@@ -1721,7 +1721,7 @@ All interceptor methods are optional—it's up to the implementor to choose whic
 
 ### Interceptor examples
 
-{/*TODO use snipsync*/}
+{/* TODO use snipsync */}
 
 **Log start and completion of Activities**
 

docs/dev-guide/tscript/foundations.mdx

@@ -492,7 +492,7 @@ And the total size of a gRPC message, which includes all the arguments, is limit
 Also, keep in mind that all Payload data is recorded in the [Workflow Execution Event History](/workflows#event-history) and large Event Histories can affect Worker performance.
 This is because the entire Event History could be transferred to a Worker Process with a [Workflow Task](/workers#workflow-task).
 
-{/*TODO link to gRPC limit section when available */}
+{/* TODO link to gRPC limit section when available */}
 
 Some SDKs require that you pass context objects, others do not.
 When it comes to your application data—that is, data that is serialized and encoded into a Payload—we recommend that you use a single object as an argument that wraps the application data passed to Activities.

docs/dev-guide/tscript/observability.mdx

@@ -131,7 +131,9 @@ export async function greet(name: string): Promise<string> {
 </details>
 
 {/*
+
 #### Customizing Activity logging with `ActivityOutboundCallsInterceptor`
+
 FIXME(JWH): Quick introduction to `ActivityOutboundCallsInterceptor.getLogAttributes()`.
 */}
 
@@ -163,7 +165,9 @@ export async function myWorkflow(name: string): Promise<string> {
 The Workflow Context Logger tries to avoid reemitting log messages on Workflow Replays.
 
 {/*
+
 #### Customizing Workflow logging using `WorkflowOutboundCallsInterceptor`
+
 FIXME(JWH): Quick introduction to `WorkflowOutboundCallsInterceptor.getLogAttributes()`.
 */}
 

docs/develop/python/asynchronous-activity-completion.mdx

@@ -0,0 +1,55 @@
+---
+id: asynchronous-activity-completion
+title: Asynchronous Activity Completion
+sidebar_label: Asynchronous Activity Completion
+description: Complete an Activity without waiting for execution to finish, using Temporal Client and Activity Function.
+slug: /develop/python/asynchronous-activity-completion
+toc_max_heading_level: 2
+keywords:
+  - asynchronous activity completion
+  - temporal python activities
+  - async activity execution
+  - temporal task token
+  - temporal activity heartbeat
+  - async activity updates
+  - temporal client for activities
+  - activity function async completion
+tags:
+  - python
+  - python-sdk
+  - activities
+  - asynchronous-completion
+---
+
+## Asynchronously complete an Activity
+
+**How to Asynchronously complete an Activity**
+
+[Asynchronous Activity Completion](/activities#asynchronous-activity-completion) enables the Activity Function to return without the Activity Execution completing.
+
+There are three steps to follow:
+
+1. The Activity provides the external system with identifying information needed to complete the Activity Execution.
+   Identifying information can be a [Task Token](/activities#task-token), or a combination of Namespace, Workflow Id, and Activity Id.
+2. The Activity Function completes in a way that identifies it as waiting to be completed by an external system.
+3. The Temporal Client is used to Heartbeat and complete the Activity.
+
+To mark an Activity as completing asynchronously, do the following inside the Activity.
+
+```python
+# Capture token for later completion
+captured_token = activity.info().task_token
+activity.raise_complete_async()
+```
+
+To update an Activity outside the Activity, use the [get_async_activity_handle()](https://python.temporal.io/temporalio.client.Client.html#get_async_activity_handle) method to get the handle of the Activity.
+
+```python
+handle = my_client.get_async_activity_handle(task_token=captured_token)
+```
+
+Then, on that handle, you can call the results of the Activity, `heartbeat`, `complete`, `fail`, or `report_cancellation` method to update the Activity.
+
+```python
+await handle.complete("Completion value.")
+```