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.26.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.26.0
File Size Uploaded
mccode_plumber-0.26.0.tar.gz 109.0 kB Details

Built distribution (wheel)

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

Total release size: 196.5 kB

Release files / mccode_plumber-0.26.0.tar.gz

Download URL mccode_plumber-0.26.0.tar.gz
Size 109.0 kB
Tags Source
SHA-256 checksum
How to use checksums
2bb35e6064929c27ff2787b47d86df16f31623e860873aa96a8272d118d08d75
BLAKE2b-256 checksum
How to use checksums
00ce93838f6307b6ecd593d3ee8f00dd46875ca84b83ab351519d3da6f2d6c55
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 16, 2026.

Transparency log

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

Download URL mccode_plumber-0.26.0-py3-none-any.whl
Size 87.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
af21dab281fb6e29cfdff0587b252507a5dd69365be6e0066a017d09faabc75f
BLAKE2b-256 checksum
How to use checksums
ab6184f1979e1234b524bd272e0a0e88df968d5e241f766c1250145edb9b8d4a
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 16, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.26.0 This release

2 release files

0.25.1

2 release files

0.25.0

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