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.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

sciforge_build-2026.7.3.tar.gz (18.4 kB view details)

Uploaded Jul 4, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

sciforge_build-2026.7.3-py3-none-any.whl (21.0 kB view details)

Uploaded Jul 4, 2026 Python 3

File details

Details for the file sciforge_build-2026.7.3.tar.gz.

File metadata

Download URL: sciforge_build-2026.7.3.tar.gz
Upload date: Jul 4, 2026
Size: 18.4 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/6.1.0 CPython/3.13.13

File hashes

Hashes for sciforge_build-2026.7.3.tar.gz
Algorithm	Hash digest
SHA256	`298947a6750a64147564e052ec911cb498b241eaa0209ca8dfd08343ceaa5e72`
MD5	`dcc23f3cf71ca2b36b10b0334441c86b`
BLAKE2b-256	`aba3ba84a113082ef9f08a43a48f60b9a3b392b2da6f90a8631d24aee064b27c`

See more details on using hashes here.

Provenance

The following attestation bundles were made for sciforge_build-2026.7.3.tar.gz:

Publisher: release.yml on RECHE23/sciforge

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: sciforge_build-2026.7.3.tar.gz
- Subject digest: 298947a6750a64147564e052ec911cb498b241eaa0209ca8dfd08343ceaa5e72
- Sigstore transparency entry: 2064681820
- Sigstore integration time: Jul 4, 2026
Source repository:
- Permalink: RECHE23/sciforge@8da1e0cf725168e3f1d03b03381637a80d5b5b85
- Branch / Tag: refs/tags/v2026.7.3
- Owner: https://github.com/RECHE23
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: release.yml@8da1e0cf725168e3f1d03b03381637a80d5b5b85
- Trigger Event: push