This is an automated email from the ASF dual-hosted git repository.

chaokunyang pushed a commit to branch update_1.2.0_grpc_python_guide
in repository https://gitbox.apache.org/repos/asf/fory-site.git


The following commit(s) were added to refs/heads/update_1.2.0_grpc_python_guide 
by this push:
     new 56970db51b Clarify Python gRPC async support timeline
56970db51b is described below

commit 56970db51beec55a8bf1f4299a5ff96c7cec2651
Author: 慕白 <[email protected]>
AuthorDate: Tue Jun 16 23:32:04 2026 +0800

    Clarify Python gRPC async support timeline
---
 docs/guide/python/grpc-support.md                                      | 3 ++-
 .../current/guide/python/grpc-support.md                               | 1 +
 .../version-1.2.0/guide/python/grpc-support.md                         | 1 +
 versioned_docs/version-1.2.0/guide/python/grpc-support.md              | 3 ++-
 4 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/guide/python/grpc-support.md 
b/docs/guide/python/grpc-support.md
index 65db689e63..3341c8c65a 100644
--- a/docs/guide/python/grpc-support.md
+++ b/docs/guide/python/grpc-support.md
@@ -34,7 +34,8 @@ instances, and Python iterators or generators for streaming 
RPCs. The generated
 stub accepts any channel configured by your application. The compiler does not
 generate `grpc.aio` stubs or service bases, so do not implement generated
 servicer methods as `async def` unless you add a custom adapter outside the
-generated companion.
+generated companion. Python gRPC async support based on `grpc.aio` will be
+available in the next Fory release.
 
 ## Install Dependencies
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guide/python/grpc-support.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guide/python/grpc-support.md
index dd2bb93f70..cfb91360ca 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guide/python/grpc-support.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guide/python/grpc-support.md
@@ -30,6 +30,7 @@ message bytes,请使用标准 protobuf gRPC 代码生成。
 `grpc.server(...)`、标准 `grpc.Channel` 实例,并用 Python iterator/generator 处理 
streaming RPC。
 生成的 stub 可以接收应用自行配置的任意 channel。Compiler 不会生成 `grpc.aio` stub 或 service
 base,因此不要把生成 servicer 方法实现成 `async def`,除非你在生成 companion 外自行封装 adapter。
+基于 `grpc.aio` 的 Python gRPC async 支持将在下一个 Fory 版本提供。
 
 ## 添加依赖
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2.0/guide/python/grpc-support.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2.0/guide/python/grpc-support.md
index dd2bb93f70..cfb91360ca 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2.0/guide/python/grpc-support.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.2.0/guide/python/grpc-support.md
@@ -30,6 +30,7 @@ message bytes,请使用标准 protobuf gRPC 代码生成。
 `grpc.server(...)`、标准 `grpc.Channel` 实例,并用 Python iterator/generator 处理 
streaming RPC。
 生成的 stub 可以接收应用自行配置的任意 channel。Compiler 不会生成 `grpc.aio` stub 或 service
 base,因此不要把生成 servicer 方法实现成 `async def`,除非你在生成 companion 外自行封装 adapter。
+基于 `grpc.aio` 的 Python gRPC async 支持将在下一个 Fory 版本提供。
 
 ## 添加依赖
 
diff --git a/versioned_docs/version-1.2.0/guide/python/grpc-support.md 
b/versioned_docs/version-1.2.0/guide/python/grpc-support.md
index 65db689e63..3341c8c65a 100644
--- a/versioned_docs/version-1.2.0/guide/python/grpc-support.md
+++ b/versioned_docs/version-1.2.0/guide/python/grpc-support.md
@@ -34,7 +34,8 @@ instances, and Python iterators or generators for streaming 
RPCs. The generated
 stub accepts any channel configured by your application. The compiler does not
 generate `grpc.aio` stubs or service bases, so do not implement generated
 servicer methods as `async def` unless you add a custom adapter outside the
-generated companion.
+generated companion. Python gRPC async support based on `grpc.aio` will be
+available in the next Fory release.
 
 ## Install Dependencies
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to