pymdf4
pymdf4.load_mf4(path, keep=None, skipped=None, *, start=None, end=None) loads scalar numeric MDF 4
channels using mdf4-rs. path may be a string or pathlib.Path. The optional
keep predicate receives each non-time channel name; rejected names are
appended to skipped when supplied. Arrays, composite channels, text, and
unsupported channel types are omitted. Invalid samples become NaN.
The optional start and end bounds select timestamps inclusively, in the
same units as the recording's timeline. Omit either for an open-ended range.
When a bound is supplied, records with NaN timestamps are excluded. Bounds
cannot be NaN, and start must not exceed end.
The result has a source string and one of these forms:
ReplayData:timelineis a list of sorted unique times andchannelsis a dictionary mapping each name to a NaN-padded list of values.SparseReplayData:timelineis a NumPy array andseriesmaps each name to a pair of NumPy arrays(times, values). Time arrays are shared between channels with the same time base.
The default pymdf4.DENSE_LIMIT is 10,000,000 cells. Set it before calling
load_mf4 to select a different limit. NumPy is required for sparse results.
Groups without a channel named time use sample indices for their time base.
For bounded loads, the local mdf4-rs crate streams supported non-interleaved
groups in bounded chunks and decodes only matching samples. It can skip data
outside the range for groups using sample indices; explicit timestamps must be
scanned, and compressed blocks must be decompressed to inspect them. Unbounded
loads and unsupported indexed layouts fall back to reading the entire file.
The loader supports DT, DV, DZ, DL, and HL data blocks; other layouts, including
LD blocks, are not supported.
File loading and Rust data processing release the Python GIL, and independent
groups and output columns are processed in parallel. The keep predicate and
Python result creation still run with the GIL held. Sparse arrays use Rust-owned
memory and cannot be resized in place.
The vendored mdf4-rs/ package is based on crate version 0.7.0 and retains
its original licenses.
For indexed inspection and selected-channel reads, open a recording
with recording = pymdf4.MdfFile(path), where path is a string or Path:
recording.structure()returns a list of groups, each withindex,name,channels, andrecord_count. Group indices distinguish repeated names.recording.timeline(group)returns timestamps in record order, andrecording.time_bounds(group)returns their minimum and maximum, orNonewhen there are no non-NaN timestamps.recording.channel_count(group, name)returns the group's record count for the named channel.recording.channel_slice(group, name, start, end)returns(times, values)for record indices fromstartinclusive toendexclusive. Indices beyond the record count are clipped.recording.channel_time_slice(group, name, start, end)returns the same pair for an inclusive time range. Both slices preserve record order.
Finalized indexed reads support scalar numeric channels in non-interleaved groups;
duplicate channel names within a group are rejected. A group without a channel
named time uses sample indices as timestamps. Time slices exclude NaN
timestamps, and time_bounds ignores them. Explicit time ranges require scanning
the group's timestamps. Unsupported indexed layouts, including interleaved record
IDs and nested conversions, return errors instead of falling back to full loading.
Keep the recording unchanged while its MdfFile index is in use.
For groups with explicit timestamps, the first channel_time_slice scans and
indexes that group's timestamps. Later slices reuse the index and read only the
span containing matching records, so narrow windows are faster when timestamps
are mostly in order. The index uses approximately 16 bytes per non-NaN sample
until the MdfFile is released. Unsorted timestamps remain supported but may
require reading a larger span. This cache does not apply to load_mf4.
For continuous reads, use the streaming methods on MdfFile:
recording.stream_start(0.0, [(646, "MisfDet_stcEmiMisfCntrCyl_[1]")])
try:
while True:
try:
samples = recording.stream_read(timeout=5.0)
except StopIteration:
break
print(samples)
finally:
recording.stream_stop()
stream_start(start, channels) starts a background reader. Channels may be
unique names or (group_index, name) pairs; use pairs for ambiguous names.
Only scalar numeric channels are supported, and the same channel cannot be
selected twice. Calling stream_start again replaces the existing stream.
stream_read() returns None immediately while any active channel needs data.
stream_read(timeout=seconds) instead waits up to the specified non-negative,
finite number of seconds and raises TimeoutError if data is still unavailable.
A timeout of zero checks immediately and raises TimeoutError if not ready.
When data is available, either form returns a dictionary keyed by the requested
channel identifiers with one (timestamp, value) per channel. A channel that finishes before the others has
the value None. When all channels finish, it raises StopIteration. Samples
retain each group's record order and are not synchronized across groups;
NaN timestamps are excluded. Background read errors raise RuntimeError.
Groups without a time channel use record indices as timestamps.
stream_set_pos(time) discards buffered data and starts again at the inclusive
time, and stream_set_channels(channels) replaces the selection from the
greatest timestamp already returned (or the start/seek position before any
read). Both operations restart reading in the background. With unsorted
timestamps, the latter can repeat or omit earlier records. stream_stop()
stops and joins the worker; it is safe to call more than once. Prefetching is
bounded per channel, but startup and seeking may require scanning records before
the requested time. The recording must remain unchanged while streaming.
For unfinalized recordings, MdfFile recovers record counts and indexes
interleaved fixed-size records without modifying the file. This supports direct
DT data blocks and the standard finalization flags for channel group counts,
the final DT length, and variable-length data sizes. Variable-length records
are skipped during scalar reads. When the DT length needs recovery, only a
single header-only DT block extending to the end of the file is supported.
Other finalization flags, layouts, and reads
from variable-length channel groups are rejected. The index stores an offset
per record, and opening an unfinalized file scans its data.
This recovery applies to MdfFile; load_mf4 has separate parser limitations.
Build wheels with maturin 1.9.4 or newer. For a manual extension build, set
PYO3_BUILD_EXTENSION_MODULE=1 when running cargo build. On Windows, copy
the resulting target/debug/pymdf4.dll to pymdf4.pyd and put it on Python's
import path. Run Rust tests with cargo test without that environment variable.
The integration tests require numpy and asammdf and can be run with
python -m unittest discover -s tests -v after building the extension.
Wheels built with maturin include the Python type stubs and py.typed marker.
The wheel workflow builds and smoke-tests CPython 3.10 through 3.15 wheels
for Linux x86-64 (manylinux 2.28), Windows x86-64, and macOS x86-64 and
ARM64. Pushing a release tag of the form x.y.z, such as 0.2.0, builds
the wheels and attaches them to a GitHub release after all builds succeed.
The workflow can also be run manually; it then publishes a release only if a
release version tag points at the selected commit, and otherwise just builds
artifacts. Use a tag matching the package version in Cargo.toml.
To publish those release wheels, manually run publish-test-pypi.yml or
publish-pypi.yml with the release tag. Each index must have a trusted
publisher configured for this repository, the corresponding workflow file,
and its GitHub environment (testpypi or pypi). See the
PyPI trusted publisher documentation.
These workflows publish wheels only and skip files already present on the index.
Run python examples/load_testdata.py to load and summarize the bundled
testdata/11-bit-obd2.MF4 recording.
Run python examples/read_mdf_structure.py to list its groups and channels.
Run python examples/inspect_mf4.py [path] for timeline and channel slice
operations; the path defaults to testdata/11-bit-obd2.MF4.
Run python examples/stream_mf4.py for streaming reads, seeking, and channel
selection using testdata/test.mf4; use --help for other recordings.
License
Licensed under either the MIT license or the Apache License, Version 2.0, at your option.
Metadata
Release files for pymdf4-rs 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 13.3 MB
Release files / pymdf4_rs-0.2.0-cp315-cp315-win_amd64.whl
| Download URL | pymdf4_rs-0.2.0-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 444.8 kB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e582a8475cfefbc136890ee1edf1f293a2f06646f4247a8ddc5e8674d8dc3ec1
|
|
BLAKE2b-256 checksum How to use checksums |
f1ae65ca547e69d0e81ddbba1a08bd67c1d392c972978e7e78de42affbc6fe01
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp315-cp315-manylinux_2_28_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp315-cp315-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 644.2 kB |
| Tags | CPython 3.15 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
19bf566c384965ffb0454870233765378d0944f4cd45800c6d658a651fa8868b
|
|
BLAKE2b-256 checksum How to use checksums |
18c76ce0cdefc0e7fe90255c2c0e7ac2e8fcbd7f774e5718772e920803e25cf4
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | pymdf4_rs-0.2.0-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 555.9 kB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a906f750608c3867d8668acaf4aa4f648a0f3b433ec86dda6707a56005cfc434
|
|
BLAKE2b-256 checksum How to use checksums |
331f4ddba64d5ac7e6ffdf274f26fb93a92cb30daf24ce5717f35f710e417c8c
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp315-cp315-macosx_10_12_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp315-cp315-macosx_10_12_x86_64.whl |
|---|---|
| Size | 570.4 kB |
| Tags | CPython 3.15 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
c088131d33bd6f1a54e348e0392c71c299edfe8fb91b049981cc357eeaefff7f
|
|
BLAKE2b-256 checksum How to use checksums |
b626e934f69784da5efdb061e86abe687b2437a4164cfcbed8a2de22c482e498
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp314-cp314-win_amd64.whl
| Download URL | pymdf4_rs-0.2.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 444.2 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
962921998e6127b369226a8df7fd901b0337045bb9e6f5d5866db2f86c09d484
|
|
BLAKE2b-256 checksum How to use checksums |
6d535b5b8ced2b2c7f2c5033d075c3d6b65d5138167b473a88fd61286ad23a07
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp314-cp314-manylinux_2_28_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp314-cp314-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 644.3 kB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e5b1bca152e326b4dad4fff6e995911897f2c357a11e60e0ddf8b73315649a7e
|
|
BLAKE2b-256 checksum How to use checksums |
837fa2e5fb4f350628368f17c6858f1efb1127f86e8f2c994a9dde0ad0c02485
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | pymdf4_rs-0.2.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 555.8 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c1711c55bf6d26f62c76298dbc80c074469dbb404673b01d22dfb0c647807bdb
|
|
BLAKE2b-256 checksum How to use checksums |
8d5af51a562c22acc1e92d21f61346857f9acf2f4e7598ae6163d3e2d60d902c
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp314-cp314-macosx_10_12_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp314-cp314-macosx_10_12_x86_64.whl |
|---|---|
| Size | 570.0 kB |
| Tags | CPython 3.14 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
5de386a978dd21dfbbd1d8e3bf12725db0b12864ea7e483cb5571a9b29eda595
|
|
BLAKE2b-256 checksum How to use checksums |
c8197294bac28137de41393993e9d2211e63f9932629bc0c46e9e89988fb8e87
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp313-cp313-win_amd64.whl
| Download URL | pymdf4_rs-0.2.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 444.5 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8b7e58a55cb67831e9b47e57206fb1ace6b3b139e0c342df9f9bc1bdb5219150
|
|
BLAKE2b-256 checksum How to use checksums |
fb512edfd3c94285ec241a2bcca24219de2ed37b2a0cc3f7fb5e7f310a82402e
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 643.4 kB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
11d1c06e1ca363b0ae2dc5097e201dbfabaf5e96c9ced39c661ae021b8e3d460
|
|
BLAKE2b-256 checksum How to use checksums |
d1e658ba71bdadbcd6f7aa0eb642cd24408dbf33cc9088a2b0fbb16b46a96155
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pymdf4_rs-0.2.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 554.6 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
90a9cb17082dae0c5776aa3147e6918965f2dd6103b703bf78ef2485f489725b
|
|
BLAKE2b-256 checksum How to use checksums |
ae5df8a481b023bfbb03a43755542e20715c3ac576871e7692bb21ea5cd75573
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp313-cp313-macosx_10_12_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp313-cp313-macosx_10_12_x86_64.whl |
|---|---|
| Size | 569.1 kB |
| Tags | CPython 3.13 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
6710a692c6ddc595546a9cb249d7ea4ba725377d8280bd910fe0e0aecc3c3a0d
|
|
BLAKE2b-256 checksum How to use checksums |
decf9577027c687472864a199f8601b13c165ce56e5e1ab33c256ff62c8b1e74
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp312-cp312-win_amd64.whl
| Download URL | pymdf4_rs-0.2.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 445.2 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
81a827cc6651ac266cc510ac13c307c928f5a699946149b4262619805a90c608
|
|
BLAKE2b-256 checksum How to use checksums |
f67643502f5aec7e43d41bceb8597fd0f540b55446393cd28259e2be6063670b
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 642.5 kB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
4a7fe691adb9c2e29032034b2a8263ac55ecc85f22d78c5c0767b77fb75ff0db
|
|
BLAKE2b-256 checksum How to use checksums |
b88ab9dcedf6eba911883a84bb19788d4bf6fc70230c9aae562ce721561e7daf
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pymdf4_rs-0.2.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 554.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
dc0884bcfb36671a6c4c0c98650ae3aa3bff767428bf6a6416d4483fc7a97582
|
|
BLAKE2b-256 checksum How to use checksums |
879c5f6ce086828cdc4c57fdab5c15e79eb750c84755ee802bc83abc3e8263ff
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 568.8 kB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
c8e89e13b91b1be140924d5fd6649a1773a448b6628ba71e7caae68ed4e0c8ed
|
|
BLAKE2b-256 checksum How to use checksums |
92e3810a98f5a2d0f2005cd2f4f9d89c83f9c673fb7fd20c33502f88ad209664
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp311-cp311-win_amd64.whl
| Download URL | pymdf4_rs-0.2.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 449.6 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e10cc41401220b686a2cdbd19837d150b157427ada3b2f2749cb997404c29f57
|
|
BLAKE2b-256 checksum How to use checksums |
7e087b3075448608b231ebf474b749a3b29dd946dfec5fdab3b396468bb1e19f
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 649.4 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ab6d3ceee943ce935266752ced23e38c1ceda211f11955a4265618272102a515
|
|
BLAKE2b-256 checksum How to use checksums |
2da1b7fa0708a63048c0d7b383f8ff3a66d4913994496e1c1cbecd4fe5c13040
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pymdf4_rs-0.2.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 561.5 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9e539effb08eb59dcb3bb2e251ba7799bd913bbf460a6e15ea98a507706df228
|
|
BLAKE2b-256 checksum How to use checksums |
cbbfdfbf11cd02e55339fb763e49355fd200db34ccfed97496bd6d072b71a779
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 570.2 kB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
ac125e13f624d3fc0bff2b2b768417c9535c07f6695764c8e2f373ed866c6d31
|
|
BLAKE2b-256 checksum How to use checksums |
102c55468342471bd379dafedaa984f593c0862ea3be53c4f5c5b812810c01eb
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp310-cp310-win_amd64.whl
| Download URL | pymdf4_rs-0.2.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 449.4 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f6da015e689fd061aed917d141b1fbcae2876a6495d13c8115d74c6b9529ab42
|
|
BLAKE2b-256 checksum How to use checksums |
dc78b92b62cb53ec55a628c165900bf6808f8f682466f16f136da3a19c12cafc
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp310-cp310-manylinux_2_28_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp310-cp310-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 650.0 kB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
cc067623460c8f327ed9d6dc33cd1cc7bd48536657835f3d065059fa085fbb0c
|
|
BLAKE2b-256 checksum How to use checksums |
665e39d6cd4fba4fea1c6e86c0831ee5b71c5227e375f1e2b88e8ddb86a0fa4d
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | pymdf4_rs-0.2.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 562.2 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
28a954f558dbdfffac320c9ef6dbf9f6ea979516f1a5905acaeeda67a41bb47a
|
|
BLAKE2b-256 checksum How to use checksums |
af83dd052effab61b268b1771a04bd85beefaafe025c2d1d3555906ba97078f0
|
| 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 Nov 13, 2026.
Transparency logRelease files / pymdf4_rs-0.2.0-cp310-cp310-macosx_10_12_x86_64.whl
| Download URL | pymdf4_rs-0.2.0-cp310-cp310-macosx_10_12_x86_64.whl |
|---|---|
| Size | 570.6 kB |
| Tags | CPython 3.10 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
bb30a65e4aef2d81a61259ba86f54f5a284fd9d267d42c8fa236156a68c33418
|
|
BLAKE2b-256 checksum How to use checksums |
9104e3fc4cd4fbe5e3e7e47adda60f15bb85bc368a65dfdb98d98f2f859350e8
|
| 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 Nov 13, 2026.
Transparency logSecurity for pymdf4-rs 0.2.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 24 files in this release have been uploaded with provenance metadata.
Attestation for pymdf4_rs-0.2.0-cp315-cp315-win_amd64.whl
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 Nov 13, 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.