northcel-vello — optional Vello renderer for NorthCel
Python binding for the NCIR v2 → Vello/wgpu renderer. It is the tolerance
tier: Vello uses analytic area antialiasing, so edge pixels differ from the
Python reference's aa x aa subpixel integration. The reference remains the
exact, normative tier.
Install from PyPI as the optional extra (per-platform wheels are built by
.github/workflows/vello.yml):
pip install "northcel[vello]"
Build locally for the host platform:
bash packaging/scripts/build_vello.sh
API used by the NorthCel launcher:
import northcel_vello
northcel_vello.render_frame(ncir_bytes, "frame.png") # -> JSON receipt string
northcel_vello.render_sequence([...], "out_dir") # -> JSON list
northcel_vello.adapter() # -> adapter info JSON
The module never parses .ncel and never falls back silently: the CLI raises a
clear install error when northcel[vello] is not installed.
Metadata
Release files for northcel-vello 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| northcel_vello-0.7.0-cp312-cp312-win_amd64.whl | CPython 3.12 | CPython 3.12 | Windows x86-64 | Details for northcel_vello-0.7.0-cp312-cp312-win_amd64.whl |
| northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64 | Details for northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_x86_64.whl |
| northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_aarch64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ ARM64 | Details for northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_aarch64.whl |
Total release size: 10.5 MB
Release files / northcel_vello-0.7.0-cp312-cp312-win_amd64.whl
| Download URL | northcel_vello-0.7.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5eca17a57d94cbe80e2fa30675da3414b4877a27ba03cfd144d3373c9cd45a68
|
|
BLAKE2b-256 checksum How to use checksums |
78db8713e6d3517f1dc0ed5caa0901a69b8fc35baf975dbc561381c0448bebe5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.5 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e647e969075db9168c2016d659216b4806b962b78ca24258e263a05fead4ade4
|
|
BLAKE2b-256 checksum How to use checksums |
6b0e66b72e3463f6c6a73ef2f824a5dd46547ddb613c827a9b5a33b5b2f893c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_aarch64.whl
| Download URL | northcel_vello-0.7.0-cp312-cp312-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
5df1b213be59eecf67306c0450cc20ae5d6d1cc4c64038085498d176d3dab6b4
|
|
BLAKE2b-256 checksum How to use checksums |
5c6e67b2757b2314ac0a42b07d0b3641b8584eee7d0fe38b17428af473f4dedb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for northcel-vello 0.7.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.