-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Heisenbug when installing with --constraint #10824
Comments
There is another report I just received on this at aboutcode-org/scancode-toolkit#2808 In this other report the dependency resolution error happens elsewhere on another dep.
|
This might be an issue around wheel compatibility, that's manifesting as a dependency resolution issue? |
At some point in the process I was getting the same conflict but on a different dependency. |
It could well be, but how can I investigate and solve the issue? I kinda grok a little the pip internals and I understand it is really hard to provide a proper actionable feedback. But if an experienced person cannot figure things out, then we have a problem to solve because that's IMHO an important breakage in the pip UX and a regression from before the introduction of the resolver in pip. If there is any wheel incompatibility on any wheel, we should return a message saying so such as :
So, what would you suggest I do to diagnose and resolve this issue here? And how can I help fix this pip UX otherwise? |
yeah, this makes this a real heisenbug as the errors are not always the same. |
I wonder if that's related to this reproducible example: #10391 (comment) In that case the user is able to get different conflict error messages to display on different runs, I have reproduced their example locally. |
I can confirm that #10391 (comment) looks very similar. |
@Hritik14 I recall you have a mac ... may be you could test this? This would be super gentle of you! ❤️ |
@pombredanne Sure. ; wget https://github.com/nexB/scancode-toolkit/releases/download/v30.1.0/scancode-toolkit-30.1.0_py36-macos.tar.xz
; tar -xf scancode-toolkit-30.1.0_py36-macos.tar.xz
; cd scancode-toolkit-30.1.0
; PYTHON_EXECUTABLE=python3 ./configure Although, I get a different package:
|
To my surprise, I could manually do ; pip install thirdparty/MarkupSafe-2.0.1-cp36-cp36m-macosx_10_9_x86_64.whl and the error now turns to
Then this followed ; pip install pyahocorasick==1.4.2
; ./configure Which fails again with
After a few iterations (of different packages and installing them manually). I finally arrived to pip install intbitset==2.4.1
|
@Hritik14 Thank you ++ for helping there! Could you try this too?
because there is a prebuilt wheel version bundled. |
With Python 3.9, use instead https://github.com/nexB/scancode-toolkit/releases/download/v30.1.0/scancode-toolkit-30.1.0_py39-macos.tar.xz that contain the proper macOS wheels |
@pombredanne ; python --version
Python 3.9.10
; ./configure
...
The conflict is caused by:
scancode-toolkit 30.1.0 depends on bitarray<3.0.0 and >=0.8.1
The user requested (constraint) bitarray==2.1.0
...
; . bin/activate
(scancode-toolkit-30.1.0) ; pip install thirdparty/bitarray-2.1.0-cp39-cp39-macosx_10_14_x86_64.whl
ERROR: bitarray-2.1.0-cp39-cp39-macosx_10_14_x86_64.whl is not a supported wheel on this platform.
WARNING: You are using pip version 21.2.3; however, version 21.3.1 is available.
You should consider upgrading via the '/Users/neo/Contrib/test-scancode/scancode-toolkit-30.1.0/bin/python -m pip install --upgrade pip' command.
scancode-toolkit-30.1.0) ; pip install bitarray==2.1.0 # installed Same iteration with |
@Hritik14 Thank you ++ |
It would be helpful to have run logs as mentioned in #10391 (comment)
|
It seems you're trying to install |
I ran into this same problem. Here are the things that were the same.
Here are things that were different.
|
@jtran Thanks. May be the use of constraints (which are somewhat new) is part of the problem? |
Description
OS: macOS v11.6
pip: 21.2.3
Python 3.6.
ScanCode Toolkit is using a --constraint installation that fails sometimes. For instance on macOS with Python 3.6
wget https://github.com/nexB/scancode-toolkit/releases/download/v30.1.0/scancode-toolkit-30.1.0_py36-macos.tar.xz
tar -xf scancode-toolkit-30.1.0_py36-macos.tar.xz
cd scancode-toolkit-30.1.0
./configure
--> this runs:pip install --no-index --find-links `pwd`/thirdparty --upgrade --no-build-isolation --editable . --constraint requirements.txt
which fails sometimes with the cryptic message:
intbitset==2.4.1
is available as a pre-built wheel under thirdparty/ alrightI am at lost to find a way to diagnose the issue. These kind of issues started randomly with the new resolver.
The pip version used is the one bundled in the included https://github.com/pypa/get-virtualenv/raw/20.7.2/public/virtualenv.pyz
that I include in my etc/thirdparty for easy bootstrapping
Expected behavior
I would like to be able to trace the installation issue.
pip version
21.2.3
Python version
3.6
OS
macOS v11.6
How to Reproduce
ScanCode Toolkit is using a --constraint installation that fails sometimes. For instance on macOS with Python 3.6
wget https://github.com/nexB/scancode-toolkit/releases/download/v30.1.0/scancode-toolkit-30.1.0_py36-macos.tar.xz
tar -xf scancode-toolkit-30.1.0_py36-macos.tar.xz
cd scancode-toolkit-30.1.0
./configure
Output
See above for details
Code of Conduct
The text was updated successfully, but these errors were encountered: