dolfinx-solver
pip install dolfinx-solver installs dolfinx-solver-complex,
the complex-scalar build of DOLFINx (FEniCSx) with PETSc and SLEPc inside the
wheel. This project ships no binaries of its own — it exists so the bare name
resolves to a working default.
PETSc's scalar type is baked into the binaries, so the real-scalar build is a
separate distribution, dolfinx-solver-real, published later. Install that
name directly when you want real scalars.
Linux x86_64 only. See the repository for the installation constraints (MPICH-family MPI, one environment per install).
1 maintainer
Metadata
1 maintainer
Release files for dolfinx-solver 0.11.0.post0
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 |
|---|---|---|---|---|
| dolfinx_solver-0.11.0.post0.tar.gz | 16.3 kB | With provenance | Details for dolfinx_solver-0.11.0.post0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dolfinx_solver-0.11.0.post0-py3-none-any.whl | Python 3 | none | any | Details for dolfinx_solver-0.11.0.post0-py3-none-any.whl |
Total release size: 33.4 kB
Release files / dolfinx_solver-0.11.0.post0.tar.gz
| Download URL | dolfinx_solver-0.11.0.post0.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15e7f97e78e5f86b16c82c155b360676db836d2c1008b09cacdec7d9010610ce
|
|
BLAKE2b-256 checksum How to use checksums |
32725971a5d0cd9c1165c50674c4c34d3f142b6fceff31f54924b2e8cd60f59a
|
| 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 13, 2026.
Transparency logRelease files / dolfinx_solver-0.11.0.post0-py3-none-any.whl
| Download URL | dolfinx_solver-0.11.0.post0-py3-none-any.whl |
|---|---|
| Size | 17.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a833e53ade42db4c919e7e038ce57525ff3832cadb182f1cee7431273cf6595f
|
|
BLAKE2b-256 checksum How to use checksums |
0dda2d7714c4c0427f50b3fdb0eb7f1e01ff73524cf45f6b03f4fb962da711fc
|
| 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 13, 2026.
Transparency logSecurity for dolfinx-solver 0.11.0.post0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for dolfinx_solver-0.11.0.post0.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 Sep 13, 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.
