-
-
Notifications
You must be signed in to change notification settings - Fork 416
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
PDM misdetects platform tag, leading to version selection that breaks resolution #3341
Comments
|
You didn't mention but apparently you are using |
Yes that is true, I don't think it has to do with unearth (but I suppose the problem is in the lockfile, and I don't know the exact interaction between PDM and uv in generating that). |
Is this related? #2696 |
I can't reproduce using the main branch, can you confirm? |
@frostming I would like to, do you have instructions on how to run it for my colleague? |
Instructions on run what? |
@frostming How to install PDM from the main branch, on macOS. |
She uses PDM from Homebrew. |
|
@frostming The fault persists on her system. I'm still trying to get hold of the log. The new uv resolution overrides functionality did provide a workaround, by the way. |
The issue exists in the lock file, and there is no torch version compatible with MacOS 14 x86_64. In fact, I forgot to mention in the docs that cross-platform lock targets are unavailable in UV mode. You may need to remove the MacOS x86_64 target, turn off uv mode, and run |
@frostming Thanks. There does exist a compatible |
Context for the interested reader: astral-sh/uv#3347 |
Describe the bug
This happens on macOS x86_64, the latest torch version that's available for this platform is 2.2.2.
To reproduce
Expected Behavior
Selection of compatible
torch
version (2.2.2).Environment Information
pdm -v output
No response
Additional Context
Full repository at https://gitlab.com/han-aim/research/knowledgeplatform/app/-/tree/ea2d531552edb9f8832d83a564203d92274186b6
Are you willing to submit a PR to fix this bug?
The text was updated successfully, but these errors were encountered: