cad-ccx
CalculiX's finite-element solver, ccx, packaged as a Python wheel, with a small launcher. It is what
text-to-cad's cad[calculix] installs, and works on its own too.
pip install cad-ccx
ccx -v # This is Version 2.23
import cad_ccx
cad_ccx.executable() # the bundled ccx program
done = cad_ccx.run("beam.inp") # runs it in beam.inp's folder, on one thread; raises cad_ccx.CcxError on failure
print(done.dat.read_text()) # what it printed to beam.dat
Unofficial. This is not the CalculiX project and is not affiliated with it. CalculiX is by Guido Dhondt and
Klaus Wittig: https://www.calculix.de. The ccx program here is conda-forge's build of the CalculiX source,
unmodified.
What a wheel holds
One platform's ccx and the libraries it loads, read from the binary's own headers and nothing more:
| Platform | Wheel tag | Files |
|---|---|---|
| Linux x86_64 | manylinux_2_17_x86_64 |
ccx, reference BLAS and LAPACK, ARPACK, GCC's Fortran, OpenMP and support runtimes |
| Linux aarch64 | manylinux_2_17_aarch64 |
the same |
| macOS Intel | macosx_11_0_x86_64 |
the same, with LLVM's OpenMP |
| macOS Apple silicon | macosx_11_0_arm64 |
the same, with LLVM's OpenMP |
| Windows x64 | win_amd64 |
the same as DLLs beside ccx.exe, with winpthreads and Microsoft's C runtime |
BLAS and LAPACK are the reference (netlib) builds rather than OpenBLAS: CalculiX's sparse solver, SPOOLES, carries
its own kernels, so a static solve barely uses BLAS, and the reference builds add no threads of their own.
Each wheel's cad_ccx/_bin/manifest.json names every conda package it came from, with its URL and sha256.
The launcher
cad_ccx.executable() |
The bundled program's path; FileNotFoundError in an install without one |
cad_ccx.version() |
The CalculiX release bundled, "2.23" |
cad_ccx.run(inp, *, threads=1, timeout=None, env=None, check=True) |
Runs ccx -i <job> in the input's folder with every CalculiX thread variable set to threads; returns a cad_ccx.Run (returncode, stdout, stderr, errors: the *ERROR lines, ok, dat, frd, output(suffix)); raises cad_ccx.CcxError when it fails, unless check=False |
ccx (the command), python -m cad_ccx |
The bundled program with your arguments |
The launcher reads and writes no CalculiX file: building a deck and reading its results are the caller's.
Building
A wheel is a repackaging, not a compile. hatch_build.py downloads the platform's pinned conda-forge packages
(pins.json: URL and sha256 of each, checked), unpacks the files pins.json lists for it, and tags the wheel.
Any machine builds any platform's wheel:
CCX_PLATFORM=win-64 python -m build --wheel # linux-64, linux-aarch64, osx-64, osx-arm64, win-64
Building from the sdist does the same, so it needs network access to conda-forge. Downloads are cached in
CCX_CACHE (default: the user's cache folder).
scripts/pins.py regenerates pins.json: it resolves CalculiX's dependencies against conda-forge's own index,
with the reference BLAS and LAPACK, and records each platform's files (scripts/closure.py) and wheel tag. Bump
CALCULIX there and version in pyproject.toml and src/cad_ccx/__init__.py together.
CI (.github/workflows/wheels.yml) builds every wheel and the sdist, tests each wheel on its own platform (the
launcher, and a cantilever solved against beam theory), and publishes to PyPI through trusted publishing whenever main carries a version not yet released: a
push that bumps the version releases it, and the workflow then tags the commit v<version>. A v* tag publishes
too.
Versions
A release's version is the CalculiX release it carries (2.23.0 carries CalculiX 2.23). A fix to the packaging
alone is a post-release (2.23.0.post1), the same CalculiX.
Licences
The launcher and build scripts are MIT (LICENSE). A wheel also distributes:
| Component | Licence | Text |
|---|---|---|
CalculiX ccx |
GPL-2.0 | LICENSES/CalculiX.txt |
| Reference BLAS and LAPACK | BSD-3-Clause | LICENSES/LAPACK.txt |
| ARPACK-NG | BSD-3-Clause | LICENSES/ARPACK-NG.txt |
| GCC's libgfortran, libquadmath, libgomp, libgcc_s | GPL-3.0 with the GCC Runtime Library Exception 3.1 | LICENSES/GCC-runtime.txt |
| LLVM's OpenMP (macOS) | Apache-2.0 with LLVM exception | LICENSES/LLVM.txt |
| mingw-w64 winpthreads (Windows) | MIT | LICENSES/mingw-w64-winpthreads.txt |
| Microsoft Visual C++ runtime (Windows) | Microsoft's redistribution terms | LICENSES/Microsoft-Visual-C-Runtime.txt |
Source for every binary: the CalculiX source at https://www.calculix.de and the conda-forge recipes and
packages each wheel's manifest.json names (https://github.com/conda-forge).
Metadata
Release files for cad-ccx 2.23.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 |
|---|---|---|---|---|
| cad_ccx-2.23.0.tar.gz | 49.9 kB | With provenance | Details for cad_ccx-2.23.0.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| cad_ccx-2.23.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for cad_ccx-2.23.0-py3-none-win_amd64.whl |
| cad_ccx-2.23.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details for cad_ccx-2.23.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| cad_ccx-2.23.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details for cad_ccx-2.23.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
| cad_ccx-2.23.0-py3-none-macosx_11_0_x86_64.whl | Python 3 | none | macOS 11.0+ x86-64 | Details for cad_ccx-2.23.0-py3-none-macosx_11_0_x86_64.whl |
| cad_ccx-2.23.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for cad_ccx-2.23.0-py3-none-macosx_11_0_arm64.whl |
Total release size: 50.7 MB
Release files / cad_ccx-2.23.0.tar.gz
| Download URL | cad_ccx-2.23.0.tar.gz |
|---|---|
| Size | 49.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30d0f5508e0a8ab744cc85bc8961da41da289173d21cfd0c40f8bf74dceb8b6c
|
|
BLAKE2b-256 checksum How to use checksums |
eb27ab38b7dae54e937ebe13172843ccf9a7ca9238e0d0108d07f0ea4e97796f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 8, 2026.
Transparency logRelease files / cad_ccx-2.23.0-py3-none-win_amd64.whl
| Download URL | cad_ccx-2.23.0-py3-none-win_amd64.whl |
|---|---|
| Size | 12.3 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9419c178f2737ea120d9a79f5db995006b0e3c2303844e7fcda7a6bdb21ec2da
|
|
BLAKE2b-256 checksum How to use checksums |
cac955324b495a085fcb8c353d25bec3cd13ee8e8aeea8beaebcdfc4b559ac32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 8, 2026.
Transparency logRelease files / cad_ccx-2.23.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | cad_ccx-2.23.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 12.1 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
521488aa8be9e768a5014d00d8c4d320dba6f94fe6609afc038ecd6f99c6a233
|
|
BLAKE2b-256 checksum How to use checksums |
8ec6382935f20aadb338672067db85295781b1b00f6df6ee2d5dd8f602501ecf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 8, 2026.
Transparency logRelease files / cad_ccx-2.23.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | cad_ccx-2.23.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 9.6 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
078d3953c7f987455a7cdd9f868039e869b3002c7307b5ee4a0c1eb84c19ec9e
|
|
BLAKE2b-256 checksum How to use checksums |
2102f47e32053999f5813ee6a49d662926e657b4605eec397454592d686dc86a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 8, 2026.
Transparency logRelease files / cad_ccx-2.23.0-py3-none-macosx_11_0_x86_64.whl
| Download URL | cad_ccx-2.23.0-py3-none-macosx_11_0_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | Python 3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
c6916ba2ec7dcaa26896a38c6806c3469512981fc15cab80ed8ead1005065a5e
|
|
BLAKE2b-256 checksum How to use checksums |
dc3a8f4921f82e69a18b76bd89c156fb12b7f88d8eec25b90dfe1fea26834612
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 8, 2026.
Transparency logRelease files / cad_ccx-2.23.0-py3-none-macosx_11_0_arm64.whl
| Download URL | cad_ccx-2.23.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 7.6 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
12f391ff46526a4d4a332f004a2efb8178807b0fa11efa4cd38b04688c0653ca
|
|
BLAKE2b-256 checksum How to use checksums |
8c356ff62d5f8a5c463328068bf78dc0da5d8f12182a09bbb4c209dc1522de41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 8, 2026.
Transparency logSecurity for cad-ccx 2.23.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 6 files in this release have been uploaded with provenance metadata.
Attestation for cad_ccx-2.23.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 Nov 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.