dirigent-storage-s3
The s3:// storage backend for dirigent, for AWS S3 and any S3-compatible endpoint.
Registers the s3 URI scheme and an s3 connection kind. URIs are s3://bucket/key; the
bucket is always carried by the URI, never inferred.
- Reads stream.
open_readyields bounded chunks off the object body, so copying a multi-gigabyte artifact is never resident. - Writes are all-or-nothing. A small write lands as one
put_object. Once the buffer crosses 5 MiB it becomes a multipart upload, completed only on a clean exit and aborted on any exception, so a reader never sees a half-written object. - Listing takes a prefix or a glob. The fixed part of the pattern becomes the S3
Prefix; the returned keys are filtered withfnmatch, so*matches across/. - Any S3 API. Set
endpoint_urlandpath_styleto address a self-hosted or third-party S3-compatible endpoint; leave both alone for AWS S3 itself.
The s3 connection check does a head_bucket when the connection names a default bucket and
a list_buckets otherwise, and reports rather than raises.
Integration tests run against a real S3-compatible server under the s3 marker, which the
default test lane excludes: uv run pytest packages/dirigent-storage-s3 -m s3.
Metadata
Release files for dirigent-storage-s3 0.23.4
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 | |
|---|---|---|---|---|
| dirigent_storage_s3-0.23.4.tar.gz | 8.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dirigent_storage_s3-0.23.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.2 kB
Release files / dirigent_storage_s3-0.23.4.tar.gz
| Download URL | dirigent_storage_s3-0.23.4.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
817fd701b389fdcf5980495942ed3a9d3302a6c0d6c7deac8ce183801062b17a
|
|
BLAKE2b-256 checksum How to use checksums |
ab724c4bf853ac995bf9910d1cff334a89fe0b07d37d8128311b1efd99934084
|
| 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 22, 2026.
Transparency logRelease files / dirigent_storage_s3-0.23.4-py3-none-any.whl
| Download URL | dirigent_storage_s3-0.23.4-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
debfe4e6573311bad75c3565fbec3adf4aa7c6c30ef2b172c764f268fdcd0aee
|
|
BLAKE2b-256 checksum How to use checksums |
3bc627d9a7f2a98068fd2e217cfc146239fc2092d3d4b84a6e196cb26a29db98
|
| 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 22, 2026.
Transparency logSecurity for dirigent-storage-s3 0.23.4
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dirigent_storage_s3-0.23.4.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 22, 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.