dagster-shared

library1.13.20pypypi✓ verified 25d ago

dagster-shared is an internal utility library providing common code, constants, and data structures shared between the core `dagster` package and other `dagster-` prefixed libraries (e.g., `dagster-dg-core`). It is not intended for direct use by end-users. The current version is 1.12.22, and it typically releases weekly or bi-weekly, synchronized with `dagster` core releases.

workflow data

pip install dagster-shared

github ↗package ↗

INSTALL

IMPORT

SIG · DAGSTER-SHARED

dagster-shared

workflowpythonv1.13.20

Install

3.7s avg

Import

—

Disk

31MB

Pass rate

10/ 10

Env Coverage10 / 10

glibc

3.9–3.13

musl

3.9–3.13

Install & Compatibility

Where this runs

tested against v1.13.20 · pip install

no network on importno background threads

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

py 3.10–3.95 runs

installs and imports cleanly · install 0.0s · import 0.000s · 32.6MB

glibc

py 3.10–3.95 runs

installs and imports cleanly · install 3.7s · import 0.000s · 33MB

31MB installed

● package 31MB

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

version

✓ from dagster_shared import version

✗ from dagster import AnyDagsterSymbol

dagster-shared is an internal dependency and does not offer a direct quickstart for end-users. User code should typically interact with the `dagster` library directly. This example shows a basic Dagster asset definition, which internally leverages components from `dagster-shared`.

from dagster import Definitions, asset @asset def my_first_asset(): return 123 defs = Definitions(assets=[my_first_asset]) # To run this, you would typically use the `dagster` CLI, e.g., `dagster dev` # and load the Definitions from a Python file or module. # dagster-shared itself does not have a direct user-facing quickstart as it's an internal utility.

Debug

Known issues

gotchaDirect imports from `dagster_shared` are generally discouraged. This library provides internal utilities and its API is not considered stable for public consumption. Symbols you might expect to find here are usually re-exported through the main `dagster` package.

fix

Always prefer importing Dagster-related symbols directly from the top-level `dagster` package (e.g., `from dagster import ...`) instead of `dagster_shared`.

affects: All versions

breakingAs an internal library, `dagster-shared` does not guarantee API stability for direct users. Breaking changes may occur without specific deprecation cycles or warnings in minor releases if you are importing directly from it.

fix

Avoid direct imports from `dagster_shared`. Rely on the stable APIs provided by `dagster` and other user-facing `dagster-*` libraries. If a specific utility is needed, check if it's available via a stable `dagster` import path.

affects: All versions

Upgrade

Version history

1.13.20latest on PyPI · released Aug 27, 2026

Audit

Dependencies

No dependency data recorded yet.

Agent activity

24 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/dagster-io/dagster ↗

packagehttps://pypi.org/project/dagster-shared/ ↗