Skip to main content

Workbench Bridges — DEPRECATED

⚠️ This package is deprecated and no longer maintained.

All functionality has been merged into the main Workbench package. New code should depend on workbench directly. Existing deployments will continue to work — this PyPI release is frozen, not removed.

Migration

workbench_bridges import workbench replacement
from workbench_bridges.endpoints.fast_inference import fast_inference from workbench.endpoints.fast_inference import fast_inference
from workbench_bridges.endpoints.async_inference import async_inference from workbench.endpoints.async_inference import async_inference
from workbench_bridges.api import ParameterStore from workbench.endpoints.parameter_store import ParameterStore
from workbench_bridges.api import DFStore from workbench.endpoints.df_store import DFStore
from workbench_bridges.api import InferenceStore from workbench.api import InferenceStore
from workbench_bridges.api import PublicData from workbench.api import PublicData
from workbench_bridges.utils.execution_environment import running_as_service from workbench.utils.execution_environment import running_as_service
from workbench_bridges.aws.sagemaker_session import get_boto3_session from workbench.core.cloud_platform.aws.boto_session import get_boto3_session

Lambda / model-script code that previously installed workbench-bridges for its lightweight AWS surface should now pip install workbench — the core install is endpoint-safe (boto3 / pandas / sklearn / scipy / rdkit) with heavy orchestration deps moved to optional extras (workbench[aws], workbench[modeling], workbench[ui]).

The workbench.endpoints.* namespace is the contract for code running inside SageMaker endpoint containers — see Workbench's scripts/endpoint_import_smoke.py for the enforced surface.

Historical context

This package originally existed to give end-user applications a small, fast-installing way to invoke deployed Workbench endpoints and read/write AWS Parameter Store, DataFrame Store, etc., without pulling in Workbench's full orchestration dependencies. The Workbench package now provides that same lightweight surface via workbench.endpoints.* and its restructured optional-extras layout, so a separate bridges package is no longer needed.

Release files for workbench-bridges 0.2.11

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for workbench-bridges 0.2.11
File Size Uploaded
workbench_bridges-0.2.11.tar.gz 48.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for workbench-bridges 0.2.11
File Interpreter ABI Platform
workbench_bridges-0.2.11-py3-none-any.whl Python 3 none any Details

Total release size: 88.8 kB

Release files / workbench_bridges-0.2.11.tar.gz

Download URL workbench_bridges-0.2.11.tar.gz
Size 48.9 kB
Tags Source
SHA-256 checksum
How to use checksums
51c2e107e4e8031233453b42b36cf3ef6f0b829e14c8ce1572d860241669991f
BLAKE2b-256 checksum
How to use checksums
8bda2806ad2ecdba5bc3a7cff872b0d9626fae54ca4316e730f484090d75cbe2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 May 22, 2026.

Transparency log

Release files / workbench_bridges-0.2.11-py3-none-any.whl

Download URL workbench_bridges-0.2.11-py3-none-any.whl
Size 39.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1d54d87a00dbd616900f017552a9aa2ae36b275fc386e9a966bfe79480f042ef
BLAKE2b-256 checksum
How to use checksums
e6ee5c2ee2338923cfd8a14bd017ba2a30abec19833117973fdbbd835b237b80
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 May 22, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.11 This release

2 release files

0.2.10

2 release files

0.2.9

2 release files

0.2.8

2 release files

0.2.7

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.18

2 release files

0.1.17

2 release files

0.1.16

2 release files

0.1.15

2 release files

0.1.14

2 release files

0.1.12

2 release files

0.1.11

2 release files

0.1.10

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page