-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
--no-pre-install-wheels --requirements-pex .. --layout packed
gives [Errno 21] Is a directory: '.../.deps/....whl'
errors
#2391
Comments
You won't like the answer here - although a bug, the fix will be merely to make the error message a controlled one. This is the ~same case as here, which I did catch when adding this feature: Lines 284 to 289 in 27c2db2
Fixing this (and the code above) will only be possible with the completion of #2299. I have #2299 all but done, but I've been side-tracked working on the lock update support Pants needs; so won't be circling back to that until #2373 ships. |
Pex cannot yet handle turning installed wheel chroots back into wheel files (see pex-tool#2299). As such, until that time, it must reject attempts to combine PEXes with different wheel packaging. Clarifies pex-tool#2391
Perfectly happy with "unsupported, but we can make the error message better". |
The OP is not solved since it relies on functionality forthcoming in #2299; so I'll leave this issue open but stop progress / un-assign for now. |
It seems pex emits "Is a directory" errors referring to wheels for invocations that use all three of
--requirements-pex ... --no-pre-install-wheels --layout packed
.For instance:
Output:
Output with PEX_VERBOSE=1 on second invocation
Details of the full 3×3 grid of requirements/outputs layouts
As part of my investigation, I wondered whether the layout of the
--requirements-pex
mattered. It doesn't seem to, but here's what I did. Script that does all of them:The text was updated successfully, but these errors were encountered: