PyAsc development wheels

pyasc-dev provides PyAsc and its experimental AscTile programming model. It installs the asc Python package. Use a dedicated environment; do not install pyasc and pyasc-dev together.

Install

Wheels support these Linux targets:

Use the matching interpreter below. Other Python/architecture combinations, macOS, and Windows are not provided.

python3.11 -m venv .venv  # Use python3.10 on AArch64.
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install --pre pyasc-dev
python -c 'from asc.experimental import asctile; print(asctile.__file__)'

CANN is required to compile and execute kernels and is installed separately. Kernel execution also needs a C++17 compiler and matching Python headers (g++ and the development headers for the selected Python interpreter). The initial runtime smoke uses CANN 9.0.0 and the Ascend950PR_9599 simulator. This is a development release, not broad numerical or hardware qualification.

Build

GitHub Actions checks the default branch of compiler-team-ru/pyasc hourly and supports manual dispatch. The GitCode-to-GitHub mirror is maintained separately. Both targets share an exact source SHA and a development version per run. Each build uses PYASC_SETUP_EXPERIMENTAL=1. An unchanged source and recipe are skipped while a successful artifact remains available. Artifacts expire after 90 days.

The builders use Ubuntu 22.04 for AArch64 and Ubuntu 24.04 for x86_64, with the exact LLVM archive in ci/toolchain.json, as specified by the selected PyAsc source instructions. The x86_64 LLVM archive requires a newer glibc than Ubuntu 22.04 provides. Each architecture has its own pinned archive. A changed LLVM download URL stops the build for review. The x86_64 builder compiles CPython 3.11 from a checksum-pinned official source archive.

Only the package description and required LLVM/zstd license notices are added to the exported source. Compiler and runtime code are unchanged. auditwheel checks the ABI and bundles zstd for the AArch64 build that needs it. The resulting wheel is checked for unexpected files and installed in two fresh environments outside the source directory.

Each target artifact contains exactly one wheel, build-passport.json, and SHA256SUMS. Build trees, caches, logs, SDKs, and source checkouts are excluded. The passport records build inputs and the actual scope of checks. The wheel metadata also records the source, LLVM, and recipe identifiers, so provenance survives artifact expiration.

Publish

Scheduled builds never publish. To publish a checked artifact, manually run wheels.yml with its successful build run ID, publish_target, and the wheel's full SHA256. Publish each qualified target separately. The publishing job downloads and verifies that artifact; it does not rebuild it.

Trusted Publisher settings:

Before publishing, run the CANN smoke on the exact downloaded wheel in a clean environment outside the repository, with WHEEL_VERSION set to its version and the exact wheel installed:

source /usr/local/Ascend/cann-9.0.0/set_env.sh
export LD_LIBRARY_PATH="$ASCEND_HOME_PATH/tools/simulator/Ascend950PR_9599/lib:${LD_LIBRARY_PATH:-}"
python -I /path/to/ci/runtime-smoke.py compile
python -I /path/to/ci/runtime-smoke.py model

The smoke tests one float32 addition. It does not measure hardware performance. PyPI versions are immutable: a new build must use a new development version.

Build provenance

Source: 3bec0127fe75b332c5f35bf10b6c130f77b3c069 in compiler-team-ru/pyasc.

LLVM: cd708029e0b2869e80abe31ddb175f7c35361f90; archive SHA256: 6399a16ba26de4dda18fa9353839ab9fcd89753e2f0baf73212019a324ee8e46.

Recipe SHA256: ca4d1786cfcc547e0e4209cc46395bb081d61108efe47545840936911f685a3e.

Recipe commit: 0eb55ac32ea977f915c425997adae593928c523f in compiler-team-ru/pyasc-wheels.