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.25.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.25.1
File Size Uploaded
mccode_plumber-0.25.1.tar.gz 105.4 kB Details

Built distribution (wheel)

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

Total release size: 191.0 kB

Release files / mccode_plumber-0.25.1.tar.gz

Download URL mccode_plumber-0.25.1.tar.gz
Size 105.4 kB
Tags Source
SHA-256 checksum
How to use checksums
391096fbde600b721ecde82aaba7e4687df9eb23d3eb5db1af26bdc940873370
BLAKE2b-256 checksum
How to use checksums
7f900debe2842e9b180447e46de35581b88579d21ea8490be3b12f6764339d5f
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 14, 2026.

Transparency log

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

Download URL mccode_plumber-0.25.1-py3-none-any.whl
Size 85.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fdc5a338772e26d1afcb5082a53a21c080580ef35598d0ed493f19987e79c57f
BLAKE2b-256 checksum
How to use checksums
1f04f248b2592149982194f3dd5087e118c50fc63af5c2007fedb63f976f1fb7
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 14, 2026.

Transparency log

Release history Release notifications | RSS feed

0.26.0

2 release files

This release

0.25.1 This release

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