pyusp — Uniscribe (usp10) OpenType shaping tracer (Windows / Linux / macOS wheel)
PyO3 abi3 wheel (pyusp-…-py3-none-win_amd64.whl) wrapping the pyusp Rust
engine. Shapes in-process via a Uniscribe implementation and returns the
babelsoft /api/opentype/shape engine dict.
from pyusp import shape_with_uniscribe
res = shape_with_uniscribe(font_bytes, text) # script auto-detected
res = shape_with_uniscribe(font_bytes, text, script="mong")
Engines. The wheel ships wineusp.dll, Wine's open-source Uniscribe port
(LGPL), which also provides a real per-lookup trace (trace=True). It drives
the OS usp10.dll (Microsoft Uniscribe) as the authoritative reference — the
Microsoft DLL is not bundled in the published wheel (it is an OS component
and not redistributable); the engine loads it from the system at runtime. A
dev/test-only build (python/build_wheel.ps1) may additionally pin an
app-local copy of usp10.dll; see python/pyusp/NOTICE.md and
python/pyusp/NOTICE-wineusp.md.
Native Microsoft trace (Windows). With backend="textshaping", trace=True
(on Windows x64) the engine hooks the system TextShaping.dll apply driver
and returns a native per-application glyph-run timeline straight from the
Microsoft engine (stages named textshaping apply N). This trace has no
lookup names (the engine does not expose them) and is only enabled on
validated TextShaping.dll builds (Win11 24H2 / 10.0.26100 x64) — anything
else raises a clear error. See python/pyusp/NOTICE-native-trace.md.
from pyusp import shape_with_uniscribe
res = shape_with_uniscribe(font_bytes, text, backend="textshaping", trace=True) # Windows
Scope note: usp10 only recognises legacy OpenType script tags. Fonts that
use only modern tags (e.g. Devanagari faces exposing dev2, not deva) are
not shaped by Uniscribe at all — this matches what old Win32 apps that rely on
usp10 actually experience.
Metadata
Release files for pyusp 0.6.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 |
|---|---|---|---|---|
| pyusp-0.6.0-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details for pyusp-0.6.0-cp39-abi3-win_amd64.whl |
| pyusp-0.6.0-cp39-abi3-manylinux_2_34_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.34+ x86-64 | Details for pyusp-0.6.0-cp39-abi3-manylinux_2_34_x86_64.whl |
| pyusp-0.6.0-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details for pyusp-0.6.0-cp39-abi3-macosx_11_0_arm64.whl |
Total release size: 1.3 MB
Release files / pyusp-0.6.0-cp39-abi3-win_amd64.whl
| Download URL | pyusp-0.6.0-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 341.1 kB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
f1c9dd82af273c5146cea4cc9e7ac97198bc655e2743868932b45e9159636c52
|
|
BLAKE2b-256 checksum How to use checksums |
1bf866ab1a9da72b2959043205f3035d33247ceb8a9494f3824df717b91f4448
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 13, 2026.
Transparency logRelease files / pyusp-0.6.0-cp39-abi3-manylinux_2_34_x86_64.whl
| Download URL | pyusp-0.6.0-cp39-abi3-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 523.6 kB |
| Tags | CPython 3.9 Linux glibc 2.34+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
de265955e5b2dbe69f7393800efbdd30f92c772f03488d0fec3f425e1c582165
|
|
BLAKE2b-256 checksum How to use checksums |
6896ab5fb88bdf81d4e8eef7ea621000446543d6f097f218b6cf057076d6d2c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 13, 2026.
Transparency logRelease files / pyusp-0.6.0-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | pyusp-0.6.0-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 473.5 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
7fed5e0f3e90aabd59ba1f4db9c14082d2abff0f95a64947512e5c192cf84c19
|
|
BLAKE2b-256 checksum How to use checksums |
bd7d619936f16be82924695786579a9450c1256a6f25bf3291379cb4664e5bd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 13, 2026.
Transparency logSecurity for pyusp 0.6.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.
Full provenance
All 3 files in this release have been uploaded with provenance metadata.
Attestation for pyusp-0.6.0-cp39-abi3-win_amd64.whl
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 Sep 13, 2026.
Transparency logA 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.