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
It is evident that the version that uv selected (the current latest) doesn't have wheels for windows. Unfortunately there a no source distribution either, so this lock file just doesn't port to windows.
Looking at https://pypi.org/simple/pyqt5-qt5/
we can see that there are wheels for older versions on Windows (PyQt5-Qt5==5.15.2). Unfortunately no single version has wheels for all major platforms: PyQt5-Qt5==5.15.2 misses a wheel for macosx + arm64.
My expectation would be that uv's resolver could detect this problem and fork the requirements automatically, but it doesn't.
Admittedly this is an exceptional setup, and I would understand that it falls out of scope somehow, especially considering that it could be resolved downstream if PyQt5-Qt5 just shipped more wheels. I just thought it was similar (at least in spirit) to the problem solved by #9827, so I figured it was worth a shot.
Meanwhile, a usable workaround for me is to manually write the fork in my requirements as
Ok this is a weird one. Let's start with what uv 0.5.9 does (or older versions too, as far as I could check):
and let's look at the relevant portion of the resulting lock file. For context,
PyQt5-Qt5
is a dependency toPyQt5
:It is evident that the version that uv selected (the current latest) doesn't have wheels for windows. Unfortunately there a no source distribution either, so this lock file just doesn't port to windows.
Looking at https://pypi.org/simple/pyqt5-qt5/
we can see that there are wheels for older versions on Windows (
PyQt5-Qt5==5.15.2
). Unfortunately no single version has wheels for all major platforms:PyQt5-Qt5==5.15.2
misses a wheel formacosx
+arm64
.My expectation would be that
uv
's resolver could detect this problem and fork the requirements automatically, but it doesn't.Admittedly this is an exceptional setup, and I would understand that it falls out of scope somehow, especially considering that it could be resolved downstream if
PyQt5-Qt5
just shipped more wheels. I just thought it was similar (at least in spirit) to the problem solved by #9827, so I figured it was worth a shot.Meanwhile, a usable workaround for me is to manually write the fork in my requirements as
which I can hide away from users into a dependency group (where a user-visible requirement would be much more inconvenient).
The text was updated successfully, but these errors were encountered: