You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
0.1.3 publishes win_amd64 wheels for CPython 3.11 to 3.14, but no win_arm64 wheel and no
sdist, so a native ARM64 CPython on Windows 11 on Arm cannot install cel-expr-python. The only
working route today is an x64 CPython running under emulation.
Would you consider adding win_arm64 wheels to the release build? GitHub provides windows-11-arm hosted runners for public repositories.
For context: we evaluate CEL through cel-expr-python in a cross-platform command-line tool, and
we can qualify Windows on Arm only with the emulated x64 interpreter, which is also our slowest
CI job.
Thanks for explaining the Kokoro limitation. I have not qualified a native Windows ARM64 source build yet. PyPI 0.1.4 still has no sdist or win_arm64 wheel, so pip cannot fall back to a source build.
Could you point me to a supported Windows ARM64 build command and toolchain? The current release helper describes cibuildwheel, but I could not find ARM64-specific guidance. A source-build path would let us test this without changing your release infrastructure.
Activity
dmitriplotnikov commentedon Nov 6, 2026
Sorry for the inconvenience!
We are using Google's internal CI/CD infra called Kokoro to produce the wheels. Currently, Kokoro does not provide support for windows/arm64.
We don't have immediate plans to migrate to github-hosted runners. I will update this issue if the changes in the future.
Have you considered building the win_arm64 wheels from source?
HengYangDS commentedon Nov 7, 2026
Thanks for explaining the Kokoro limitation. I have not qualified a native Windows ARM64 source build yet. PyPI 0.1.4 still has no sdist or win_arm64 wheel, so pip cannot fall back to a source build.
Could you point me to a supported Windows ARM64 build command and toolchain? The current release helper describes cibuildwheel, but I could not find ARM64-specific guidance. A source-build path would let us test this without changing your release infrastructure.