-
Notifications
You must be signed in to change notification settings - Fork 682
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
Incompatible cached wheels may continue to be used after upgrade #3599
Comments
Unfortunately it's hard to help here without more information and a reliable reproduction. We intentionally don't key the cache on uv version -- instead, each of the buckets has its own version that we bump whenever the schema changes. |
Do you have any idea how that wheel ended up in the cache in the first place? Either way we shouldn't be re-using it unless it appears to be compatible with the current environment. Any reproduction welcome! Otherwise I may have to close. |
I think I can reproduce it by creating an alternate install using brew - do these installations share files at all?
|
Think I need to look at this with fresh eyes in the morning... I might be interested to see the output of the first |
The core problem AFAICT is that for some reason |
It would be one thing if you created the venv with |
Yeah, it's a MacBook Air (Apple M1).
|
I haven't been able to reproduce this yet. I installed an x86 Python and repeated the process above. I agree that something strange is happening above. In |
|
I've updated macOS and it shows |
Unfortunately I was never able to reproduce this even after installing both an x86 and an ARM Python side-by-side on my machine. |
I am experiencing the same error regarding installing pydantic on MacOS M1 chip:
However, pip directly selects the correct architecture and installs properly. my mac platform version:
Uninstalling pydantic and cleaning uv cache does not resolve the problem. |
I saw an issue installing pydantic on macOS where it uv would use an incompatible wheel for pydantic_core (with cp312-cp312-macosx_10_12_x86_64 tag) resulting in this error message:
pip would select a different one (with cp312-cp312-macosx_11_0_arm64 tag) which worked.
I had recently upgraded to
uv 0.1.44 (d417daad7 2024-05-14)
, and auv cache clean
fixed the issue - on reinstall it used a compatible wheel.Are the UV caches keyed off the uv version at all? Perhaps the uv installation should self-invalidate caches.
The text was updated successfully, but these errors were encountered: