Python libraries for Blackmagic Design broadcast devices: one package, one version, four device families.
pip install bmdwire
| Import | Purpose | License | Docs |
|---|---|---|---|
atemwire |
ATEM switchers: the native UDP protocol, a connection pool, macro bytecode, "Save Switcher State" profiles | LGPL-3.0-only | atemwire/README.md |
hyperdeckwire |
HyperDeck recorders: transport control and clip listing over TCP 9993, clip upload over FTP, and the deck's configuration (network, FTP / Web Media Manager / Ethernet Protocol switches, certificate, users, time) over the API HyperDeck Setup drives | MIT | hyperdeckwire/README.md |
ultimattewire |
Ultimatte 12 keyers: archive and restore over the native TCP protocol, Smart Remote 4 compatible zips | MIT | ultimattewire/README.md |
videohubwire |
Videohub routers: state snapshot, crosspoint routing, labels over TCP 9990 | MIT | videohubwire/README.md |
All four are pure standard library except atemwire, whose small C extension ships prebuilt for Linux, macOS and Windows on CPython 3.10 to 3.14, so installing needs no compiler. Pin the version in a requirements file (bmdwire==1.10.0) so a later release cannot change your install under you.
atemwire stands on pyatem
atemwire is a fork of pyatem by
Martijn Braam and the OpenAtem contributors. Years of reverse engineering
the ATEM protocol came before any of this, and that work is what made the
rest possible. It branched at upstream commit 8f45831 (2026-03-14) and was
then developed for months against live switchers: transport reliability
fixes, a declarative wire-format layer, corrected and extended message
coverage, macro upload, and profile save and restore.
The licence is unchanged and not negotiable: LGPL-3.0-only, the same as
upstream. Improvements to atemwire stay open, as they should. The other three
libraries here were written from scratch and are MIT. The distribution's
licence expression is LGPL-3.0-only AND MIT, and each package directory
carries the text that governs it.
If you want the original rather than this fork, it is at https://git.sr.ht/~martijnbraam/pyatem and it is still maintained.
Why one package
The four libraries share an author, a shape and a purpose: they are the device layer of one broadcast control application, extracted and published so others can use them. Until 1.0.x each was its own PyPI project with its own version number. Nothing downstream ever wanted them apart, and four numbers to track for one release train was confusion with no benefit, so since 1.1.0 they are one distribution: one tag, one version, one line to pin. The import names did not change.
The four old PyPI projects (atemwire, hyperdeckwire, ultimattewire, videohubwire) were deleted on 2026-09-16; bmdwire is the only package. They were not replaced by shims, on purpose: a release of atemwire that depended on bmdwire would have broken pip install -U atemwire, because pip installs the dependency first and then removes the old package's files, which are the same paths bmdwire just wrote. If an environment still has any of the four old packages from before, uninstall them before installing bmdwire (pip uninstall atemwire hyperdeckwire ultimattewire videohubwire). Two distributions owning one module directory work until one of them is uninstalled. A fresh virtualenv, a pipx install or a container build never has this problem.
Development
git clone https://github.com/lucas-romanenko/bmdwire.git
cd bmdwire
pip install -e ".[test]" # builds atemwire's C extension in place, needs a compiler
python -m pytest
The editable install matters: a plain pip install . puts the extension in site-packages, and python -m pytest run from the checkout then imports the source tree without it and fails on atemwire.mediaconvert. The suite needs no hardware. CI runs it on Python 3.10, 3.12 and 3.14 for every push and pull request, and builds an sdist and a wheel to prove the metadata.
A release is a tag v<version> on main whose version equals project.version in pyproject.toml; pushing it builds the sdist and the wheels and publishes them to PyPI. pip show bmdwire, not a hand-typed number, is how to know what is installed.
Not affiliated with or endorsed by Blackmagic Design Pty Ltd. ATEM, HyperDeck, Ultimatte and Videohub are trademarks of Blackmagic Design.
1 maintainer
Metadata
1 maintainer
Release files for bmdwire 1.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bmdwire-1.10.0.tar.gz | 392.8 kB | With provenance | Details for bmdwire-1.10.0.tar.gz |
Built distributions (wheels)
Total release size: 14.4 MB
Release files / bmdwire-1.10.0.tar.gz
| Download URL | bmdwire-1.10.0.tar.gz |
|---|---|
| Size | 392.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99c335d38ea94d6b3ccbc62ec5640e1ee778b1b6efdffbd74b60b88e7a601856
|
|
BLAKE2b-256 checksum How to use checksums |
a929334b0529c6617b404bdc2b04fbad713d3cb396e670511f254c70223d43d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp314-cp314-win_amd64.whl
| Download URL | bmdwire-1.10.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 465.5 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
28c48efba81de8af9d4099949f401ea3d2f1d6b222987e698a65f2b07ffaed07
|
|
BLAKE2b-256 checksum How to use checksums |
81ca80fd2c816aadf2dee99f95435ceaeb8a3d2c6a5ef1339740451c51bd04e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp314-cp314-win32.whl
| Download URL | bmdwire-1.10.0-cp314-cp314-win32.whl |
|---|---|
| Size | 464.8 kB |
| Tags | CPython 3.14 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
759ea31141108b0b4651d791ca9176d631efd4a5b73a1b0781810e67f3d076bc
|
|
BLAKE2b-256 checksum How to use checksums |
03e3c8b470e1b05f2af5a06f1e26f76f81a9104441ff58a38c6fbaad113f8294
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | bmdwire-1.10.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 475.9 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
55cd48a048e8f8986b00e0b8f6e228c0848157be6879f96698fdebc425f52ded
|
|
BLAKE2b-256 checksum How to use checksums |
69460596d94829562d5c067b6ef9fe5411ad2f32777fcb731d40369e38f5686c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | bmdwire-1.10.0-cp314-cp314-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 470.4 kB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
cffc7cb095e817df507a48ac9f6d4e9452ea50265de8de503d85d5b56850ad2b
|
|
BLAKE2b-256 checksum How to use checksums |
a9649dc6b4023ea127eaebc731c5ad168668b6f1947b48afa08f4ab0a3a5c227
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | bmdwire-1.10.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 460.6 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0b849ae6dbada97a555e82c8d8a24c4477b888e543f337b8977ea4d84c825304
|
|
BLAKE2b-256 checksum How to use checksums |
6b95720d4dd08b850382e6b6a15e943f7dabce0fbde4aa493b87be3c06995937
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | bmdwire-1.10.0-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 463.4 kB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
d56dec0823648c4b2e2d0c885948a3ef1ea04931ecc6bf2abf6896e6a26e5420
|
|
BLAKE2b-256 checksum How to use checksums |
c924dd215fbaa98a4635d5254f88b7ac9c35b3307a7bea60856227ec741dd810
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp313-cp313-win_amd64.whl
| Download URL | bmdwire-1.10.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 464.0 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
539d52ab182fbaea8e9361b752617b159c9f63e6e9f94d22a44bc89104ac303f
|
|
BLAKE2b-256 checksum How to use checksums |
dfcf02d695bd487af37231c54be5c5e26378a6d9500b354273019195b9a7a977
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp313-cp313-win32.whl
| Download URL | bmdwire-1.10.0-cp313-cp313-win32.whl |
|---|---|
| Size | 463.3 kB |
| Tags | CPython 3.13 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
46c11950d29ba3790008da6e0e1cd9c019e09154e8dd6fd15ed2980777bd7755
|
|
BLAKE2b-256 checksum How to use checksums |
a7d3739c1e9013fc821f3bc4ca286f26ffaa07ae210a8bce7fc6569674cfcb0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | bmdwire-1.10.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 475.9 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
6b1eebb19071bb69fd99a43bf713dc1af328034aea0dd0d64104118a302e2c54
|
|
BLAKE2b-256 checksum How to use checksums |
51214c979c0b05f2dbfecd4e2f291592326770259a03f6dd78176a250d2a9c72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | bmdwire-1.10.0-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 470.3 kB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
60ef96de07844123453e9c0774aaafe1c50c5d9f892612065d25c6978085dffd
|
|
BLAKE2b-256 checksum How to use checksums |
58486c3dd552c364bb74b5f8058020cb1c51d82a15c2304437a0fbfbb74227a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | bmdwire-1.10.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 460.6 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b91502b7f3b64ae6e3a1a89d918bad96aac5c8ba7fdabc4f5b7e5a33c6963398
|
|
BLAKE2b-256 checksum How to use checksums |
d0cf1bb0ac02ac25d9e020dfbed09a9c837862b53aaa34f1633459bb6ffc4c00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | bmdwire-1.10.0-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 463.4 kB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
b202e077026ea2c142d2ada4ce825cb72e9d5571d9e2826d746c2cd582d0f89f
|
|
BLAKE2b-256 checksum How to use checksums |
6b8af09eeb7c1fcd2f51c765f0e97d945f0ea43ad8859d93d227b71e64b3bf6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp312-cp312-win_amd64.whl
| Download URL | bmdwire-1.10.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 464.0 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f963b2414f8252b327c1a9078a8bc6187cec8d6c9248d02cebec2d1b2f6e8834
|
|
BLAKE2b-256 checksum How to use checksums |
8a6bd642c2c087dd74dc2155733afdd61b9f5d8951de34c624777b546cbbe1ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp312-cp312-win32.whl
| Download URL | bmdwire-1.10.0-cp312-cp312-win32.whl |
|---|---|
| Size | 463.3 kB |
| Tags | CPython 3.12 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
e97252d95698aedaaf8a2056595570bf0d67972a17e87cbfa53284aeb7f32118
|
|
BLAKE2b-256 checksum How to use checksums |
76679217c4613772e389845c88bb420a516db3047d92c847df92339807590e53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | bmdwire-1.10.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 475.8 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
20b615f4606746c6886f9836def14c56a755c1f363c829fd419b786d3149ac3c
|
|
BLAKE2b-256 checksum How to use checksums |
d69296f342fb802d34c53466f53ebe9f6d978771e55217c53df463d9acfc1038
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | bmdwire-1.10.0-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 470.3 kB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
fcbd7f9eec0ae8f91d1cdb90810e9886c5b37a2e1e0bf7219fb9c3a548e979ea
|
|
BLAKE2b-256 checksum How to use checksums |
c0fe0a76512aded50385a65b239c43f760d8d0c88215323328344dddcb46a418
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | bmdwire-1.10.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 460.6 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3209d3e6d21d7576a734165cd183c0415181f0551b83021684425f8d049175af
|
|
BLAKE2b-256 checksum How to use checksums |
0a8e2dd7be0896a57174f187bbc475239ba7b4f0027f89379049bc71ca2ea031
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | bmdwire-1.10.0-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 463.4 kB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
1e2f6ac6f09cfafbbafbe663b7ec7fdb1085307d4a30499a1789a9ac20519943
|
|
BLAKE2b-256 checksum How to use checksums |
73ffd7c28b19a704947b4dfef17714b4278fa717f0546e037e6fd9a94f7ac547
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp311-cp311-win_amd64.whl
| Download URL | bmdwire-1.10.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 464.0 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
2b30cd1087e56404acf1f59eefac3ced093b5516e6cbc63498300e26ad32e4c8
|
|
BLAKE2b-256 checksum How to use checksums |
7a42c696a5734c6b7023ad9d92239c11b8d8d99249dfd39efecd4a72d76556a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp311-cp311-win32.whl
| Download URL | bmdwire-1.10.0-cp311-cp311-win32.whl |
|---|---|
| Size | 463.3 kB |
| Tags | CPython 3.11 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
a5263b5dc0057195a0dd4ebd16e2b0b48feb9be80259d94a2c5d75ef3bc0b451
|
|
BLAKE2b-256 checksum How to use checksums |
f224a8f9ff1b9748bd421ba76e5d1f09de4fe4ed57c0b194e225e589ca5097c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | bmdwire-1.10.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 475.7 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
4a960db6bab81eeb20c8e9c4b2ab867fcecf33152d585cb0ba4b8c60bf567278
|
|
BLAKE2b-256 checksum How to use checksums |
592e1a5bca972030648742c64528684585edd6f4ef3e21a4858fc3570daa1c35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | bmdwire-1.10.0-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 470.1 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
9cd66daa8ed8eefa0ad7f0f6177db65c62d128a873702a07c9653a0799019487
|
|
BLAKE2b-256 checksum How to use checksums |
fdf9eca9755adeb53a1e6e99e092a197b701501a95ce40b603c5fccba3666df9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | bmdwire-1.10.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 460.5 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d0be82b6964598c7391e0f6d92c71b3d7ef1bbd3903a6cd98b1e644a2971292c
|
|
BLAKE2b-256 checksum How to use checksums |
5b4bbc4a401ef7b82de072b353428ffb5be10a6238711dc6d31bd2989cca8e73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | bmdwire-1.10.0-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 460.2 kB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
e21aa3ebc5ad7492cc2fbcb69834d21608f52a0b6508a74a24fa237543f0ada5
|
|
BLAKE2b-256 checksum How to use checksums |
2e6a3da77d54bd69eac2af8dab123f3410ce7f0441781b450efbc90a824816d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp310-cp310-win_amd64.whl
| Download URL | bmdwire-1.10.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 464.0 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
bb6be27aaf562955c8240a72c797f1b1407eac75c0a35e064391ee6f4ed3b2db
|
|
BLAKE2b-256 checksum How to use checksums |
52a3f1f7ec278af31931100fbbb8fb354fe93068747fe75dc0409203081dfe23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp310-cp310-win32.whl
| Download URL | bmdwire-1.10.0-cp310-cp310-win32.whl |
|---|---|
| Size | 463.3 kB |
| Tags | CPython 3.10 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
9ed12e67f22529e67dd7e08f14dd2b20fd72e48e27cb819bfd0fd9f9b75963d1
|
|
BLAKE2b-256 checksum How to use checksums |
349fd3ad6220171712b671cb9fcc3ecaf1837e56234f3b2b26f9724841128ed1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | bmdwire-1.10.0-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 475.7 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
a55ceb2a2a40816b3d450849b44d5f934bb15f2dcba8a66cf8321c59de4e6353
|
|
BLAKE2b-256 checksum How to use checksums |
dcdc9a67a3454ecdf4133d1fa8af3de98cf942e654593a056aacba46d9b6975e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp310-cp310-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | bmdwire-1.10.0-cp310-cp310-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 470.1 kB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
e452c07bc2152e5971c119992fec8d911166730f55a9e9fdacba9bab99d8414f
|
|
BLAKE2b-256 checksum How to use checksums |
3b8bbd65096d69412631576f4070abbcd5d302a0e4d1da6739df24450b09225b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | bmdwire-1.10.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 460.5 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
511ac372c2deccd644f780f43d321a4478bf40e997ba1c7a0474473c8b60535b
|
|
BLAKE2b-256 checksum How to use checksums |
573ec0a3f29f958996db6f09d2d1eeb639137a0570d75e8f7cd80bd5fa23dbdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / bmdwire-1.10.0-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | bmdwire-1.10.0-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 460.2 kB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
5581bec4527c7b0efcbf9979ef480c98161ae210e92988273d20126bcf32bfd5
|
|
BLAKE2b-256 checksum How to use checksums |
a4eec881c61c7cf8c7589a2f3cf1093e9faf9a1a1c0a6568b15cc1598236796d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logSecurity for bmdwire 1.10.0
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.
Full provenance
All 31 files in this release have been uploaded with provenance metadata.
Attestation for bmdwire-1.10.0.tar.gz
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 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
