vLLM-HUST Engine r8 · packaging revision2
This is the same frozen r8 runtime and all9235 checksum-pinned files. post2 changes package installation, not engine kernels, MODs, evaluation inputs or measured results.
In the qualified CPython3.12 / Linux aarch64 / CANN9.1.0 environment:
python -m pip install --no-deps -r https://github.com/vLLM-HUST/vllm-hust-website/releases/download/engine-wheels-r8-v1/r8-pip-requirements-post2.txt
The fixed requirements file explicitly lists this Engine package, the same-name vllm and vllm-ascend wheels, and the runtime support wheel, with SHA256 verification for all four. One pip operation replaces older official distributions while retaining import vllm, import vllm_ascend and the vllm CLI. --no-deps retains the externally qualified vendor environment: upstream Triton-Ascend and vLLM dependency metadata contain conflicting NumPy requirements. No dependency metadata is removed or falsified, and no separate downloader or installation script is needed. The complete original SDK and fixed evaluation tools remain included. Native artifacts are not recompiled or retagged as manylinux.
Qualified dependencies: Torch2.13.0+cpu, Torch-NPU2.13.0rc1, Triton-Ascend3.6.0, Transformers5.14.1 and tokenizers0.22.2. CANN, drivers and model weights remain external. The qualified vendor environment is a prerequisite; this command installs the four pinned engine distributions only, not Torch, Triton-Ascend, CANN or model weights. Unsupported ABI causes pip to fail. post1 was an unpublished candidate rejected during full dependency resolution; use post2 with this complete four-package manifest.
The Qwen3.5-35B-A3B BF16 / TP2 / dual Ascend910B2 MOD recipe (CorrectedWorker, BetterScale, Microflow, KV materialization, M01 correction, packed-host, sealed warmup, guarded async progress, E36/R54 and short-prefill tail; MTP2/FULL, host4GiB/rank and KV20GiB/rank) uses the frozen r8 launcher. Generic vllm serve does not select this model-specific recipe automatically.
SDK verification and evaluation remain available through vllm-hust-engine verify / install / evaluate. Installation does not start a model or create a new performance result.
Metadata
Release files for vllm-hust-engine 2026.11.17.8.post2
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 |
|---|---|---|---|---|
| vllm_hust_engine-2026.11.17.8.post2.tar.gz | 124.8 MB | Without provenance | Details for vllm_hust_engine-2026.11.17.8.post2.tar.gz |
Release files / vllm_hust_engine-2026.11.17.8.post2.tar.gz
| Download URL | vllm_hust_engine-2026.11.17.8.post2.tar.gz |
|---|---|
| Size | 124.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ccb1e14cc58840bee730832d29ac519e6ca98de5d48ecc8701a9df265c0c935
|
|
BLAKE2b-256 checksum How to use checksums |
6b559e123415bb59ad3343ed7502a6faa985729fa28546df70fe93ceb1ef9929
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for vllm-hust-engine 2026.11.17.8.post2
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.