-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Using --no-pypi --repo
produces broken pex
#1345
Comments
Your
Whichever, that interpreter is the one the built PEX file should work with. That interpreter may not be the same as the one A few useful bits of information you could provide to fully debug this remotely:
Thanks in advance. |
Hmm I'm not sure what you mean by unadorned. I've just reproduced this with the latest pex release, downloaded from github:
vs
Note the fishy thing here - a version of FWIW, python2 breaks in even worse ways, so it seems like the pex is build for python3:
Here's the extra debug output:
|
Digging around, this might be related to changes in |
Thanks for the debug output, but I need that for the PEX file you created, not for the Pex PEX file. Using your latest debug output as a guide, you'd want to add |
Ah got it. Here you go:
If it helps - here's the: pex.pex (i renamed it to pex.zip so i can upload it) |
Thanks @mikekap and sorry for the delay. If you could add two more pieces of debugging information I think I'll have all I need to diagnose what happened here. If you can, the full output of these two commands:
I'm not sure if those paths work, but the gist is: I'd like to see what the pip corresponding to each of your Python 3.8 interpreters reports for that interpreters "Compatible tags" (an O(100s) list at the bottom of the debug output). To be clear about the problem you saw: When Pex builds a PEX file it does fail fast if it cannot resolve all requirements for the interpreters and requirements you've selected. If you've selected no interpreter, it uses the default one pex is running under (you can control this with
The debug info above will help me look into 2. I suspect 1 is not the issue since you're building and running the PEX file on the same machine. |
Sorry - one more thing. In your PEX_TOOLS info output above, it shows |
Hey @mikekap I'm going to close this since it looks like you've moved on. If you can provide the extra debug information I asked for in #1345 (comment) and #1345 (comment) just above though, I'll re-open and dig more. |
Compare:
vs
The difference seems to be that the pypi build uses the wheel named
pandocfilters-1.4.3-py3-none-any.whl
while the--repo
build ends up using the file namedpandocfilters-1.4.3-cp38-none-any.whl
.Now I admit I don't quite know that this is the correct way to use
--repo
, but I would hope pex would at least raise the error when building the pex instead of at runtime.The text was updated successfully, but these errors were encountered: