sciforge-build
Build-time distribution of the SciForge C++ binding substrate headers
(<sciforge/binding/...>). It is never a runtime dependency — list it in your
build-system.requires and add sciforge_build.get_include() to your extension's
include_dirs at wheel-build time. Pure-Python (py3-none-any); CalVer, aligned with
the SciForge tag.
Resolving the headers (canonical consumption pattern)
A wheel/sdist build (pip, python -m build, cibuildwheel) resolves the headers through
the sciforge-build package above. But a co-development checkout wants the sibling
SciForge tree, not a possibly stale pip-installed package. The canonical resolver in a
consumer's setup.py tries, in order, an explicit SCIFORGE_INCLUDE override, a sibling
sciforge checkout, then the package — so local dev wins, CI/wheel falls through to the
package:
def _sciforge_include():
header = os.path.join("sciforge", "binding", "error.hpp")
env = os.environ.get("SCIFORGE_INCLUDE")
if env and os.path.exists(os.path.join(env, header)):
return env
sibling = os.path.join(os.path.dirname(os.path.abspath(__file__)), "..", "sciforge", "include")
if os.path.exists(os.path.join(sibling, header)):
return sibling
try:
import sciforge_build
return sciforge_build.get_include()
except ImportError:
raise SystemExit("sciforge headers not found: check out RECHE23/sciforge as a "
"sibling, pip install sciforge-build, or set SCIFORGE_INCLUDE")
Then include_dirs=["include", _sciforge_include()], and have the Makefile python
target export SCIFORGE_INCLUDE=$(SCIFORGE_INCLUDE) (default ../sciforge/include) so a
sibling build needs no installed sciforge-build. The exists(error.hpp) guard makes a
sibling that lacks binding/ fall through to the package.
1 maintainer
Metadata
1 maintainer
Release files for sciforge-build 2026.10.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 | |
|---|---|---|---|
| sciforge_build-2026.10.0.tar.gz | 18.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sciforge_build-2026.10.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.3 kB
Release files / sciforge_build-2026.10.0.tar.gz
| Download URL | sciforge_build-2026.10.0.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18f07adff8a76886ffcb929ae0fd8ecaa3b0a3ed1935691ccedfda4f882f4950
|
|
BLAKE2b-256 checksum How to use checksums |
7fc11842e1bd3d609f9f3173745328780790ebfa575cd4f73625d60150e07eb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Oct 2, 2026.
Transparency logRelease files / sciforge_build-2026.10.0-py3-none-any.whl
| Download URL | sciforge_build-2026.10.0-py3-none-any.whl |
|---|---|
| Size | 21.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
390fb8b70be5cd6398f840bdc936667b0aadfcfaf67fb305afa7415673719dc4
|
|
BLAKE2b-256 checksum How to use checksums |
2f489626c6088b979398496911c2d9d26faddfc5d8883652e671952085f8d517
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Oct 2, 2026.
Transparency log
