slimrpc pypackage incompatible with slim-bindings~=1.0

[codyhartsook]

Version
slim-bindings==1.0
slim-bindings==1.1

Platform
Darwin CHARTSOO-M-WHJK 25.2.0 Darwin Kernel Version 25.2.0: Tue Nov 18 21:09:56 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6041 arm64

Description

All published pypi versions of slimrpc seem to be incompatible with Python slim-bindings >= 1.0 due to a breaking API rename introduced in slim-bindings 1.0.0.

I tried the following import:

pip install slim-bindings==1.0.0 "slimrpc>=0.2.0"
python -c "import slimrpc"

I expected to see: slimrpc imports successfully.

Instead, the following import error occurred:

File "slimrpc/common.py", line 106, in <module>
    ) -> Tuple[slim_bindings.IdentityProvider, slim_bindings.IdentityVerifier]:
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'slim_bindings' has no attribute 'IdentityProvider'. Did you mean: 'IdentityProviderConfig'?

slimrpc 0.2.0 is the only version whose dependency specifier (>=0.7.1, unbounded) allows slim-bindings 1.0 to be installed, but it fails at import time. slimrpc 0.2.1 pins slim-bindings ~=0.7.1, so it will not resolve at all alongside slim-bindings 1.0.

This also affects downstream consumer slima2a (0.2.1-0.2.2)

A new slimrpc release referencing the renamed APIs would resolve the issue. Alternatively, backward-compatible aliases in a future slim-bindings release would preserve compatibility with existing consumers.

Please let me know if I have imported something incorrectly or if compiling slimrpc ourselves is the preferred approach to using slimrpc pypi.

It looks like there is an open PR to introduce slimrpc 0.2.2: #1117, will review if this fixes the issue.

[msardara]

Hey Cody! Thanks for the report 🙏

Just a heads-up: we’re planning to deprecate the standalone slimrpc PyPI package. We have migrated the slimrpc logic directly into slim-bindings via #1202. This new implementation is written in Rust, allowing us to share the core logic across multiple languages beyond just Python.

We currently have two PRs in flight to enable this for Python and Go: #1163 and #1148. Once those land, we’ll release the updated slimrpc compiler and slim-bindings. Moving forward, you’ll be able to use slimrpc simply by installing the slim-bindings wheel or the slim-bindings-go module.

Beyond Python and Go, the long-term plan is to leverage the Rust core to extend support to JS, C#, Java, and Kotlin. This will give us a unified RPC layer across our entire stack.

[codyhartsook]

Hi Mauro, thanks for the explanation. Could you provide any insight on slima2a, this package seems to use the standalone slimrpc package. For A2A integration would you recommend I should wait for slima2a to use native slim-bindings rpc or implement client and handlers directly off of slim-bingings slimrpc?

[msardara]

Once the new slim-bindings with slimrpc and the new slimrpc compiler will be out, we will update slima2a to depend only on slim-bindings and to use the new APIs.

I'd recomment you want for the new slima2a version, it should be out soon, you can follow the release in #1217 ✅

[Tehsmash]

I think we can now go ahead and close this issue as fixed, the new slim-bindings package is out with the integrated slimrpc feature.

@msardara do you know how we can mark slimrpc deprecated in pypi?