smg-grpc-proto
Protocol Buffer definitions for SMG (Shepherd Model Gateway) gRPC services.
This package provides pre-compiled Python gRPC stubs for:
- SGLang scheduler service (
sglang_scheduler.proto) - SGLang encoder service (
sglang_encoder.proto) - vLLM engine service (
vllm_engine.proto) - TensorRT-LLM service (
trtllm_service.proto)
Installation
pip install smg-grpc-proto
Requires grpcio>=1.81.1 and protobuf>=5.26.0.
Usage
from smg_grpc_proto import sglang_scheduler_pb2, sglang_scheduler_pb2_grpc
from smg_grpc_proto import sglang_encoder_pb2, sglang_encoder_pb2_grpc
from smg_grpc_proto import vllm_engine_pb2, vllm_engine_pb2_grpc
from smg_grpc_proto import trtllm_service_pb2, trtllm_service_pb2_grpc
Proto Source
The proto source files live in grpc_client/proto/ in the SMG repository. Python stubs are generated at build time using grpcio-tools and shipped in the wheel.
Development
To install in editable mode from the repo root:
pip install -e grpc_client/python/
For CI or environments where symlinks don't work:
mkdir -p grpc_client/python/smg_grpc_proto/proto
cp grpc_client/proto/*.proto grpc_client/python/smg_grpc_proto/proto/
pip install -e grpc_client/python/
Testing proto changes on a remote GPU machine
After editing .proto files locally, build a wheel and install it in the remote environment (e.g. vLLM):
# 1. Build wheel (regenerates Python stubs from latest .proto files)
cd grpc_client/python
# Copy proto files into the package tree (the repo uses a symlink which
# won't survive wheel packaging)
mkdir -p smg_grpc_proto/proto
cp ../proto/*.proto smg_grpc_proto/proto/
pip wheel . --no-deps -w dist/
# 2. Copy to remote
scp dist/smg_grpc_proto-*.whl remote-gpu:/tmp/
# 3. Install on remote (into vLLM's env or whichever env needs it)
pip install --force-reinstall /tmp/smg_grpc_proto-*.whl
No import changes are needed on the remote side — vLLM already imports from smg_grpc_proto.
License
Apache-2.0
1 maintainer
Release files for tokenspeed-smg-grpc-proto 0.4.22.post20260924
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tokenspeed_smg_grpc_proto-0.4.22.post20260924.tar.gz | 30.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tokenspeed_smg_grpc_proto-0.4.22.post20260924-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 130.8 kB
Release files / tokenspeed_smg_grpc_proto-0.4.22.post20260924.tar.gz
| Download URL | tokenspeed_smg_grpc_proto-0.4.22.post20260924.tar.gz |
|---|---|
| Size | 30.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78210d49f4a9a4c9b918c33dc59d1a63f5cc559ca3b681aca4d41191fe086364
|
|
BLAKE2b-256 checksum How to use checksums |
06253c06984d7168d655cb39d286a8a43cce5d05ca1c77363866ab7443fe8cb8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / tokenspeed_smg_grpc_proto-0.4.22.post20260924-py3-none-any.whl
| Download URL | tokenspeed_smg_grpc_proto-0.4.22.post20260924-py3-none-any.whl |
|---|---|
| Size | 100.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32b8befa6df4af23cd31fe90978c0969eec91b9035ac3197b815ade247fe43db
|
|
BLAKE2b-256 checksum How to use checksums |
61d63e180b7f48db43bd149fc3e7de1a2478e7174c228b439b00894c42376eb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency log
