-
Notifications
You must be signed in to change notification settings - Fork 95
Missing wheels for CPython 3.10 manylinux x86 since 0.0.25 #425
Copy link
Copy link
Closed
Labels
bugIssue reports a bugIssue reports a bugresolvedIssue is resolved, yet unreleased if openIssue is resolved, yet unreleased if openupstreamIssue must be taken upstreamIssue must be taken upstream
Description
Context
No response
Bug description
The published files for Zensical 0.0.24 include zensical-0.0.24-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl, but there is no corresponding wheel for Zensical 0.0.25 (but here is a cp38 wheel).
Was this a deliberate change in the release process between 0.0.24 and 0.0.25? For reference, I noticed this because a CI run failed; it didn't have the necessary toolchain to compile zensical from source, and I'd prefer to avoid having to do so.
Related links
Reproduction
This isn't something I can really provide a .zip file for, it depends on local OS/packages.
Steps to reproduce
- Run
pip install zensical==0.0.25using an image such aspython:3.11-slim
This results in the following error messages:
cargo 1.94.0 (85eff7c80 2026-01-15)
📦 Including license file `LICENSE.md`
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings with abi3 support
🐍 Found CPython 3.11 at /usr/local/bin/python3.11
📡 Using build options features from pyproject.toml
Compiling proc-macro2 v1.0.103
Compiling quote v1.0.42
Compiling unicode-ident v1.0.22
Compiling libc v0.2.178
Compiling target-lexicon v0.13.4
error: linker `cc` not found
|
= note: No such file or directory (os error 2)
error: could not compile `quote` (build script) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `proc-macro2` (build script) due to 1 previous error
error: could not compile `libc` (build script) due to 1 previous error
error: could not compile `target-lexicon` (build script) due to 1 previous error
💥 maturin failed
Caused by: Failed to build a native library through cargo
Browser
No response
Before submitting
- I have read and followed the bug reporting guidelines.
- I have attached links to the documentation, and possibly related issues.
- I assure that I have removed all customizations before submitting this bug report.
- I have attached a .zip file with a minimal reproduction.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue reports a bugIssue reports a bugresolvedIssue is resolved, yet unreleased if openIssue is resolved, yet unreleased if openupstreamIssue must be taken upstreamIssue must be taken upstream