Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Dash0 OpenTelemetry Declarative Configuration

Declarative (file-based) SDK configuration for the Dash0 OpenTelemetry Python distribution, read from OTEL_CONFIG_FILE.

The package is experimental, tracking a configuration format that is still at 1.0-rc.1.

Do not edit this package by hand

Everything under src/ and the whole of pyproject.toml are generated by scripts/vendor_configuration.py from the dash0 branch of https://github.com/dash0hq/opentelemetry-python. The UPSTREAM file records the exact commit. A hand edit here is reverted by the next run of that script, and the vendored-configuration job in CI fails while it is still present.

Two files are exempt, because the script leaves them alone: this README, and src/opentelemetry/_configuration/version/__init__.py, which holds the released version and is advanced by scripts/bump_for_release.py.

Where a change belongs

Changes to how configuration files are parsed, validated or applied go on the fork’s dash0 branch, as commits on top of an upstream commit. That is what makes them survive upstream moving: rebase the branch onto the new upstream commit, then run:

python3 scripts/vendor_configuration.py --commit <new sha>

Changes to how the code is packaged for this distribution go in scripts/vendor_configuration.py. It owns the rename from opentelemetry.configuration to opentelemetry._configuration, the re-export shims at the path the SDK imports, and the dependency pins, which it copies from the distribution’s own pins rather than repeating them.

Why the implementation sits at a private path

The implementation is installed as opentelemetry._configuration, a path upstream does not own, and opentelemetry.configuration holds only star re-export shims. opentelemetry/sdk/_configuration/__init__.py imports opentelemetry.configuration by name, so the shims are what make OTEL_CONFIG_FILE work, while the private path means installing this alongside a future published opentelemetry-configuration cannot collide file for file. The pyproto exporter packages in this workspace use the same arrangement.

What the fork changes

Upstream validates configuration files with jsonschema, which brings attrs, referencing, jsonschema-specifications and rpds-py. All four would land in the tree the injector adds to an application’s sys.path, and rpds-py is a compiled extension, so that tree would stop being pure Python. The fork compiles the schema to plain Python with fastjsonschema at development time instead, leaving a validator that imports decimal and nothing else. The fork’s own test suite checks that validator against jsonschema document by document.

Metadata

Release files for dash0-opentelemetry-configuration 0.65b0.post1

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

Source distribution (sdist)

Source distribution for dash0-opentelemetry-configuration 0.65b0.post1
File Size Uploaded Provenance Actions
dash0_opentelemetry_configuration-0.65b0.post1.tar.gz 54.0 kB With provenance Details for dash0_opentelemetry_configuration-0.65b0.post1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dash0-opentelemetry-configuration 0.65b0.post1
File Interpreter ABI Platform Actions
dash0_opentelemetry_configuration-0.65b0.post1-py3-none-any.whl Python 3 none any Details for dash0_opentelemetry_configuration-0.65b0.post1-py3-none-any.whl

Total release size: 120.0 kB

Release files / dash0_opentelemetry_configuration-0.65b0.post1.tar.gz

Download URL dash0_opentelemetry_configuration-0.65b0.post1.tar.gz
Size 54.0 kB
Tags Source
SHA-256 checksum
How to use checksums
fa1499c50294f19b3f121e34178a5e231540753cb3fc6f4408ee6f8437fe186f
BLAKE2b-256 checksum
How to use checksums
6134278f89b10aa96290881a618633106b437752e8415977c5e982e291f53c08
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 27, 2026.

Transparency log

Release files / dash0_opentelemetry_configuration-0.65b0.post1-py3-none-any.whl

Download URL dash0_opentelemetry_configuration-0.65b0.post1-py3-none-any.whl
Size 66.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ee05b9e7bb3977fc6e7bf470cacc25f2020d10ba7e3666520af6d57a2daf1eb9
BLAKE2b-256 checksum
How to use checksums
1b1d1e449df253c8dc8416fd7df026be6e2418612708f07c38e5cb17c145eec9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 27, 2026.

Transparency log

Security for dash0-opentelemetry-configuration 0.65b0.post1

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for dash0_opentelemetry_configuration-0.65b0.post1.tar.gz

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 Oct 27, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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