This release is a pre-release and may not be stable for production use.
ccp4i2
ccp4i2 is the Python backend of CCP4i2 — the graphical interface and scripting environment for the CCP4 macromolecular crystallography suite. This is the Django/Qt-free generation of CCP4i2: a REST API, a task/pipeline framework, and the data-management core that drive the CCP4i2 desktop (Electron/React) and web deployments.
CCP4-free control plane
The control plane — the REST API, task configuration, parameter validation, and the container/digest machinery — imports and runs on a stock Python with no CCP4 installation. Only actual job execution (running Refmac, Phaser, Servalcat, …) needs the full CCP4 suite, and that always happens out-of-process on a CCP4-bearing worker.
In practice that means you can pip install ccp4i2 into a plain virtual
environment to configure and validate tasks, serve the API, and drive the
frontend; the crystallographic binaries and their toolkits (clipper, iotbx,
mmtbx, ccp4mg, phaser, dials, xia2, …) are supplied by CCP4 at execution time and
are deliberately not pip dependencies.
Installation
pip install ccp4i2
Optional extras:
pip install ccp4i2[science] # rdkit, scipy, pandas — fuller local execution
pip install ccp4i2[dev] # test/lint toolchain (pytest, mypy, black, …)
ccp4i2 depends on the shared
ccp4i2-api library (authentication +
DRF integration), which is installed automatically.
Note —
demo_data(the ~400 MB of example datasets used by the test/demo workflows) is not bundled in the package; it is distributed out-of-band.
Running
export DJANGO_SETTINGS_MODULE=ccp4i2.config.settings
# i2run — run a task from the command line
i2run <task> --project_name <proj> [--PARAM value ...]
# development server
python -m uvicorn ccp4i2.config.asgi:application
Links
- CCP4: https://www.ccp4.ac.uk/
- Source: https://github.com/ccp4/ccp4i2
- Documentation: https://www.ccp4.ac.uk/html/INDEX.html
Licence
LGPL-3.0. See the repository for full licensing details.
1 maintainer
Release files for ccp4i2 3.1.0a53
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ccp4i2-3.1.0a53.tar.gz | 22.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ccp4i2-3.1.0a53-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.5 MB
Release files / ccp4i2-3.1.0a53.tar.gz
| Download URL | ccp4i2-3.1.0a53.tar.gz |
|---|---|
| Size | 22.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52b1807f0c2339d150f45c040cc32e97955c91ec5ac9c0277faae68c447bbebc
|
|
BLAKE2b-256 checksum How to use checksums |
0bb368d4c9f3cc04253cbd11b59ff815e022c1168dea55eabf8b5b8f6ae43535
|
| 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 11, 2026.
Transparency logRelease files / ccp4i2-3.1.0a53-py3-none-any.whl
| Download URL | ccp4i2-3.1.0a53-py3-none-any.whl |
|---|---|
| Size | 22.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
260a98e2afe8878000b3064e6140afed11e64c81cf83e42775f647ebe21e3121
|
|
BLAKE2b-256 checksum How to use checksums |
79941cd057978211c0cdf4c7aac15926a6ca19be79763312b1e439692b59c288
|
| 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 11, 2026.
Transparency log
