iirds-validate
The iiRDS checker now ships as iirds —
install that. This name is kept so that pip install iirds-validate keeps
working: it installs nothing of its own and depends on iirds, which carries
the checker, the iirds, iirds-validate and iirdsv commands, and the
read/write library. Tools that install by executable, such as pipx and
uv tool, want the name that has one: iirds.
Upgrading from 0.4.x: uninstall first, then install the new name with
-U — without it, the iirds library already present satisfies the request
and nothing new is installed.
pip uninstall -y iirds-validate
pip install -U iirds
The order matters: pip records each distribution's files separately and does
not notice when two records claim one path, so installing the new name first
and uninstalling the old one afterwards deletes files the new one had just
written. If that has already happened, pip install --force-reinstall --no-deps iirds restores them.
Both names are held in stewardship for the iiRDS ecosystem and will be transferred to the iiRDS Consortium on request.
1 maintainer
Release files for iirds-validate 0.6.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 | |
|---|---|---|---|
| iirds_validate-0.6.0.tar.gz | 6.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iirds_validate-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.1 kB
Release files / iirds_validate-0.6.0.tar.gz
| Download URL | iirds_validate-0.6.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccf35c667c760546542c48685acd57b6454ccb6438500beadde4c54703f86f38
|
|
BLAKE2b-256 checksum How to use checksums |
dee6d9cc1d268b51fd9cd2e4fdc308236c0fb0c2e0f5bcbe822e42017dde2afd
|
| 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 Sep 5, 2026.
Transparency logRelease files / iirds_validate-0.6.0-py3-none-any.whl
| Download URL | iirds_validate-0.6.0-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76efb01de6b1ca150f600071579f9b62c5a76cc9fa4fba8a6089fe49f7070664
|
|
BLAKE2b-256 checksum How to use checksums |
5cd6d854cd369b1ff19f3036bda7d31a5aee988dc788bdf0d60ca03e972c3c24
|
| 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 Sep 5, 2026.
Transparency log
