sap-cloud-sdk 0.52.2+ requires protobuf>=7.36.0,<8, conflicting with a2a-sdk (protobuf<7)
@ArthurTonial 已经在做这个了。
开始于 2026年9月14日。
- 主要语言
- Python
- 星标
- 28
- 派生
- 42
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 35
描述
Describe the Bug
sap-cloud-sdk 0.52.2 and above requires protobuf>=7.36.0,<8, but a2a-sdk requires protobuf>=5.29.5,<7 (as of version 1.1.4).
So sap-cloud-sdk 0.52.2 and above are incompatible with recent versions of the a2a-sdk.
Resolver output (uv):
Because a2a-sdk==1.1.2 depends on protobuf>=5.29.5,<7 and
sap-cloud-sdk==0.53.0 depends on protobuf>=7.36.0,<8, we can conclude
[that] your requirements are unsatisfiable.
Any project using sap-cloud-sdk>=0.52.2 and an a2a-sdk release that still caps protobuf<7 cannot resolve.
Steps to Reproduce
- Create an a2a agent that requires a2a-sdk 1.1.4 and sap-cloud-sdk 0.53.0 and attempt to resolve the dependencies
Expected Behavior
It needs to be possible to use a2a-sdk in combination with the sap-cloud-sdk without dependency conflicts.
Screenshots
No response
Used Versions
- Python version via
python --version: Python 3.13.13 - SAP Cloud SDK for Python version: 0.53.0
- Framework version (if applicable, e.g., Flask, FastAPI): Starlette 1.6.0 / uvicorn 0.52.4 (A2A agent server, via a2a-sdk 1.1.2)
Installed packages via pip list or uv pip list
This is the resolved set with sap-cloud-sdk==0.52.0 (the working baseline —
0.53.0 is unsatisfiable, see below). Key packages:
a2a-sdk==1.1.2
grpcio==1.83.1
httpx==0.28.1
langchain==1.4.0
langchain-core==1.6.3
langchain-litellm==0.7.1
litellm==1.96.0
protobuf==6.33.6
sap-cloud-sdk==0.52.0
starlette==1.6.0
uvicorn==0.52.4
With sap-cloud-sdk==0.53.0 the set does NOT resolve:
Because a2a-sdk==1.1.2 depends on protobuf>=5.29.5,<7 and
sap-cloud-sdk==0.53.0 depends on protobuf>=7.36.0,<8, we can conclude
that your requirements are unsatisfiable.
(Resolved with uv pip compile --python-version 3.13, 175 packages total.)
Code Examples
Stack Trace
No response
Log File
Log file
...Affected Development Phase
Getting Started
Impact
No Impact
Timeline
No response
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。