This release is a pre-release and may not be stable for production use.
engine/ — the MEIDNet engine, vendored
meidnet/ is a snapshot of the MEIDNet package at the research checkout recorded in SNAPSHOT.json
(upstream commit 26a0387862 plus the uncommitted work of the staged-evaluation rounds), and meidnet_eval/ holds the
evaluation components (the ten blocks and their bands in stages.py, the generation, judging, relaxation and
calibration scripts). Install with pip install ./engine before pip install -e .; the distribution is named
meidnet (2.4.0.dev2) so the application's meidnet>=2.2.0,<3 dependency resolves to it and nothing is fetched from PyPI.
On PyPI, meidnet 2.4.0.dev2 is this snapshot, uploaded by MEIDNet-Matter's release workflow so that pip install meidnet-matter
resolves without a clone; the upstream MEIDNet release 2.4.0 (https://github.com/ABnano/MEIDNet) will replace it.
Snapshot taken 2026-10-08. To refresh it: python scripts/vendor_engine.py --src <checkout>. The upstream release of this
work is planned as meidnet 2.4.0; when it exists, this folder is removed and the dependency pinned to that release.
1 maintainer
Metadata
1 maintainer
Release files for meidnet 2.4.0.dev2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meidnet-2.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / meidnet-2.4.0.dev2-py3-none-any.whl
| Download URL | meidnet-2.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 425.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cd56f782d13271a27d908029468224ca413f1b13df488cd52b9876ff4338bf73
|
|
BLAKE2b-256 checksum How to use checksums |
7c5cce1c020670bfa7541e38b7f742dd3e9e33889972ccbd5dfb89f091d3036f
|
| 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 9, 2026.
Transparency log
