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.post2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dash0_opentelemetry_configuration-0.65b0.post2.tar.gz | 54.1 kB | With provenance | Details for dash0_opentelemetry_configuration-0.65b0.post2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dash0_opentelemetry_configuration-0.65b0.post2-py3-none-any.whl | Python 3 | none | any | Details for dash0_opentelemetry_configuration-0.65b0.post2-py3-none-any.whl |
Total release size: 120.1 kB
Release files / dash0_opentelemetry_configuration-0.65b0.post2.tar.gz
| Download URL | dash0_opentelemetry_configuration-0.65b0.post2.tar.gz |
|---|---|
| Size | 54.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2aa64c75ed5c09be47ca40f47729b2fda13d7e9c1e68f0ea88ef1ac92aa5f40e
|
|
BLAKE2b-256 checksum How to use checksums |
2a2557cbbd49dd17e6c7b066c004e456dafc7d13c3b754e503b1ea5d38227498
|
| 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 28, 2026.
Transparency logRelease files / dash0_opentelemetry_configuration-0.65b0.post2-py3-none-any.whl
| Download URL | dash0_opentelemetry_configuration-0.65b0.post2-py3-none-any.whl |
|---|---|
| Size | 66.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cbc66cccb93af6d40a6570073bc14a9a58e92815244420d8c98e2de84d261e3b
|
|
BLAKE2b-256 checksum How to use checksums |
0a721f1bd1963c57a73c0d9624b8aa3bc4d420a6d3eaacb46813415fb4a4955f
|
| 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 28, 2026.
Transparency logSecurity for dash0-opentelemetry-configuration 0.65b0.post2
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.
Attestation for dash0_opentelemetry_configuration-0.65b0.post2.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 28, 2026.
Transparency logA 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.