modelcontextprotocol/python-sdk
Watch
1
0
Fork
You've already forked python-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: refresh translations for recent English changes (#3379)

Browse source
This commit is contained in:
Max 2026-08-24 19:29:54 +01:00 • committed by GitHub
commit c5d7d0b6d0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3149 additions and 1047 deletions
Download patch file Download diff file Expand all files Collapse all files

4
i18n/zh/pages/handlers/logging.md
View file

@ -1,6 +1,6 @@
---
translation:
sections: [c93a3e1aefd77955, 7851abd5ec54393b, f49d1ca2f330f9cd, c03764bd9dfeef7b, 4a0391691a674ae4, 2df5cd279eabf9f5]
sections: [c93a3e1aefd77955, 7851abd5ec54393b, f49d1ca2f330f9cd, 4cc0a00347c3f534, 4a0391691a674ae4, 2df5cd279eabf9f5]
tool: 1
---
# 日志 {#logging}
@ -49,6 +49,8 @@ MCP 在协议层面有一个**日志能力**（logging capability）：服务器
`logging.basicConfig()` 永远不会替换已经存在的 handler。如果你在创建服务器之前自己配置了日志，以你的配置为准。
也不需要只为了记录失败而在每个处理函数里都写 `try`/`except`。工具或资源函数抛出异常时，SDK 会替你记录下来。记录了什么、用哪个级别，详见 **[处理错误](../servers/handling-errors.md#any-other-exception)**。
## 试一试 {#try-it}
用 MCP Inspector 运行服务器：