This project has been archived by its maintainers, and is no longer receiving any updates.
httk-io
httk-io is the file input/output module for httk₂. It provides:
- the
httk.iopackage within the PEP 420 nativehttknamespace, currently a CIF/mCIF parser, reader and writer stack; and - the
httk.handlers.iopackage, which registers the.cifloader withhttk-core's plugin registry so files can be read viahttk.core.load.
Most users should install the httk2
metapackage, which selects a useful set of httk modules:
pip install httk2
Install only this module (it depends on httk-core and numpy) with:
pip install httk-io
Usage
Importing httk.core discovers httk.handlers.io and registers the .cif
loader. httk.core.load then dispatches on the file extension and returns the
raw parsed CIF data as a (data_blocks, header) tuple:
import httk.core # discovery registers the ".cif" loader
data_blocks, header = httk.core.load("structure.cif")
name, block = data_blocks[0]
print(block["cell_length_a"])
Development and release instructions are in the
RELEASING.md guide.
Metadata
Release files for httk-io 0.1.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 |
|---|---|---|---|---|
| httk_io-0.1.0.tar.gz | 41.0 kB | With provenance | Details for httk_io-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| httk_io-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for httk_io-0.1.0-py3-none-any.whl |
Total release size: 84.0 kB
Release files / httk_io-0.1.0.tar.gz
| Download URL | httk_io-0.1.0.tar.gz |
|---|---|
| Size | 41.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad5be6cd804fcd1a77fc1c292e673919c1a8afe9578d40579caf6a8757f16f17
|
|
BLAKE2b-256 checksum How to use checksums |
cd8a244c3d0e1a4fbe8728f9c1c3707ebe673494f97d90407c5700b837ba4928
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 22, 2026.
Transparency logRelease files / httk_io-0.1.0-py3-none-any.whl
| Download URL | httk_io-0.1.0-py3-none-any.whl |
|---|---|
| Size | 42.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f089744cc31a04e9c6c1e331b445ead288dcd6ce35aec409b763b9678288cf3
|
|
BLAKE2b-256 checksum How to use checksums |
0aef1c7199c843ccf44fc7bd2c803237edced52bac853d0d9f79b548eb6b8216
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 22, 2026.
Transparency logSecurity for httk-io 0.1.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 2 files in this release have been uploaded with provenance metadata.
Attestation for httk_io-0.1.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 Jul 22, 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.