Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distribution kaleido==0.2.1.post1 @ registry+https://pypi.org/simple can't be installed because it doesn't have a source distribution or wheel for the current platform #292

Open
jpedrick opened this issue Mar 10, 2025 · 5 comments
Assignees

Comments

@jpedrick
Copy link

jpedrick commented Mar 10, 2025

Using uv add or uv sync I can't install kaleido. uv pip install kaleido works without any issues.

I'm using Python 3.10 on Linux x86_64

error: Distribution `kaleido==0.2.1.post1 @ registry+https://pypi.org/simple` can't be installed because it doesn't have a source distribution or wheel for the current platform

hint: You're on Linux (`manylinux_2_35_x86_64`), but `kaleido` (v0.2.1.post1) only has wheels for the following platform: `manylinux2014_armv7l`
@ei-grad
Copy link

ei-grad commented Mar 11, 2025

I also faced this issue with uv sync, but additionaly, I can't use kaleido==0.2.1 in my pyproject.toml / requirements.lock since my project will be used for both x86_64 and arm64 targets :-(.

@ei-grad
Copy link

ei-grad commented Mar 11, 2025

Hm.. 0.2.1 does contain some ARM targets, so my additional worry is not relevant probably. Will check.

@ayjayt
Copy link
Collaborator

ayjayt commented Mar 11, 2025

Okay, so v0.2.1.post1 was an arm32-only release

v0.2.1 contained all other releases.

So, what I think is that pyproject.toml would have to to have kaleido>=v0.2.1, and I'm going to create an issue in uv to see whether or nor their dependency resolve can fork for different systems, but it may not be possible in uv yet.

@ayjayt ayjayt closed this as completed Mar 11, 2025
@ayjayt
Copy link
Collaborator

ayjayt commented Mar 11, 2025

Also, is everyone here aware of the architecture change with v1 coming out? @ei-grad @jpedrick

@ayjayt ayjayt reopened this Mar 11, 2025
@ayjayt ayjayt self-assigned this Mar 11, 2025
@ayjayt
Copy link
Collaborator

ayjayt commented Mar 11, 2025

  • Investigate uv resolving forking behavior on different architectures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants