Skip to main content

McCode Plumber

Setup, run, and teardown the infrastructure for splitrun McCode scans sending data through Kafka into NeXus

Metadata

Release files for mccode-plumber 0.22.0

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

Source distribution (sdist)

Source distribution for mccode-plumber 0.22.0
File Size Uploaded
mccode_plumber-0.22.0.tar.gz 86.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mccode-plumber 0.22.0
File Interpreter ABI Platform
mccode_plumber-0.22.0-py3-none-any.whl Python 3 none any Details

Total release size: 158.9 kB

Release files / mccode_plumber-0.22.0.tar.gz

Download URL mccode_plumber-0.22.0.tar.gz
Size 86.3 kB
Tags Source
SHA-256 checksum
How to use checksums
66c803911cf153da08d9eca66bd4b663d9115b07e77e5ad019513fd98917e19b
BLAKE2b-256 checksum
How to use checksums
9de3aaf2f56cfe67ed45ccd39c0968234a22917c0e7b6814f44794fe99dcabdf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 30, 2026.

Transparency log

Release files / mccode_plumber-0.22.0-py3-none-any.whl

Download URL mccode_plumber-0.22.0-py3-none-any.whl
Size 72.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4816be5270a3a59cc94363d5622d44f0abe7588f4e9128bebeb5d911a8d44d39
BLAKE2b-256 checksum
How to use checksums
fedd34f57b34d7cce12297bc3077eb3f37049329569a377499677cb60ee16b9d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 30, 2026.

Transparency log

Release history Release notifications | RSS feed

0.26.0

2 release files

0.25.1

2 release files

0.25.0

2 release files

0.22.1

2 release files

This release

0.22.0 This release

2 release files

0.20.1

2 release files

0.20.0

2 release files

0.19.0

2 release files

0.18.0

2 release files

0.17.6

2 release files

0.17.5

2 release files

0.17.4

2 release files

0.17.1

2 release files

0.17.0

2 release files

0.14.4

2 release files

0.14.3

2 release files

0.14.2

2 release files

0.14.1

2 release files

0.14.0

2 release files

0.12.0

2 release files

0.11.1

2 release files

0.11.0

2 release files

0.10.0

2 release files

0.9.0

2 release files

0.8.2

2 release files

0.8.1

2 release files

0.8.0

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.0

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