FinalCif
FinalCif helps you to get a complete CIF file from a single-crystal X-ray diffraction experiment. See here https://dkratzert.de/finalcif.html for details.
For tables from multiple CIF files, you may want to use the program multitable.
Report templates
You only need them if you want to make report tables that differ from the default ones.
Recent Changes
Some screenshots
(click to enlarge)
1 maintainer
Metadata
1 maintainer
Release files for finalcif 160
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 |
|---|---|---|---|---|
| finalcif-160.tar.gz | 15.8 MB | With provenance | Details for finalcif-160.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| finalcif-160-py3-none-any.whl | Python 3 | none | any | Details for finalcif-160-py3-none-any.whl |
Total release size: 16.6 MB
Release files / finalcif-160.tar.gz
| Download URL | finalcif-160.tar.gz |
|---|---|
| Size | 15.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abda7fe8020cab5745df408a533977afb0aadf1a59ce61ba09c62c522554faa8
|
|
BLAKE2b-256 checksum How to use checksums |
17f65b7f37eedf21a45cb1b948c70ebae84b4fadf2dddf4115a4d88d30e9bef1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logRelease files / finalcif-160-py3-none-any.whl
| Download URL | finalcif-160-py3-none-any.whl |
|---|---|
| Size | 806.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
80f7be308d39a02af6916ae57345e0d8fc6434f12fd086c8ebb3b03bc77338c7
|
|
BLAKE2b-256 checksum How to use checksums |
288aa3c8fabe8e6ded464ec068607075a0aacde3a30c614fcca5fe4bb8cc2269
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 8, 2026.
Transparency logSecurity for finalcif 160
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 2 files in this release have been uploaded with provenance metadata.
Attestation for finalcif-160.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 May 8, 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.
