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.23.1

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.23.1
File Size Uploaded
mccode_plumber-0.23.1.tar.gz 102.6 kB Details

Built distribution (wheel)

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

Total release size: 186.6 kB

Release files / mccode_plumber-0.23.1.tar.gz

Download URL mccode_plumber-0.23.1.tar.gz
Size 102.6 kB
Tags Source
SHA-256 checksum
How to use checksums
6159dd64c445403ac34df6799ed8d2704ef43ed05fc39671d38c2a920aa5c5b1
BLAKE2b-256 checksum
How to use checksums
660d10fd6ca4a130c83b00b17b2ebdaab64293dea4e9ea771f6f32a2d4756e73
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 Oct 7, 2026.

Transparency log

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

Download URL mccode_plumber-0.23.1-py3-none-any.whl
Size 84.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
658aa75f92a2cfdab2fef1e46d151aa8c86e867179d4e0bb07948701c7d1770e
BLAKE2b-256 checksum
How to use checksums
dbdb22e6424cc2cd3e5c1da780203413c1ba9d47c0962228b7c32d580d1e7cde
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 Oct 7, 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

This release

0.23.1 This release

2 release files

0.22.1

2 release files

0.22.0

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