-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
requirements resolution for some python_dist() target fails when 3rdparty/python/requirements.txt is modified (maybe) #6638
Comments
Also, I don't know if this is happening when I run the binary that test invokes -- I believe that it is, but I wasn't able to test that this time before running |
Should try with My understanding here is that the python interpreter cache goes looking for python interpreters on your machine that already have wheel installed. It might be that it is finding one that doesn't have wheel. |
I ran into the same issue today (on latest PEX_VERBOSE=1 ./pants test tests/python/pants_test/build_graph:target -- -k=test_has_sources Trace details
I was able to get it resolved by setting the |
|
I haven't yet been able to nail down this repro, but on both my Linux and OSX machines, after rebasing/pulling past the commit
38ccf42c49f31e26462a266e8c63fb7875bcec14
, there was an error in requirements resolution whenever I ran the below.This is from my OSX machine -- I don't believe I have logs from my Linux machine but can probably get them (but this doesn't look platform-specific). However, I'm pretty sure I saw a failure in a different requirement on Linux, but again I can't remember exactly what, and it may have been unrelated or due to local changes.
This went away after a
clean-all
. I don't know how to repro this easily so I don't know if this is e.g. just happening for #6628 (the PR I was working on), or others. I strongly suspect this is apython_dist()
bug. I believe this is more reason for #5970.I might look through the changes in setuptools, wheel, or pex from the commit above and see if any of those look likely to have caused this failure. As of now I don't have a repro yet, so I'm focusing on that first.
The text was updated successfully, but these errors were encountered: