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

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.2
File Size Uploaded
mccode_plumber-0.22.2.tar.gz 92.9 kB Details

Built distribution (wheel)

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

Total release size: 168.8 kB

Release files / mccode_plumber-0.22.2.tar.gz

Download URL mccode_plumber-0.22.2.tar.gz
Size 92.9 kB
Tags Source
SHA-256 checksum
How to use checksums
ea98c1257a6f6bcc230e621cc27e1a193083dfbcfeef579511652ad204793982
BLAKE2b-256 checksum
How to use checksums
c7d9b602c1a3f41f8b060232262f89e143d500006c21f6c9a5dcf98b8e677a76
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 1, 2026.

Transparency log

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

Download URL mccode_plumber-0.22.2-py3-none-any.whl
Size 75.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
db2ae98382d9e51649c82cb36d223036e3a6f1230e7f128f0fe961550acc3dbe
BLAKE2b-256 checksum
How to use checksums
8f8c7d9d1ad5cd8c95fabb64cb85551c406970e223c0787a52df4825c1c930dc
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 1, 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.22.2 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