-
Notifications
You must be signed in to change notification settings - Fork 54
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
make use of locked markers in lock file version 2.1 and thereby avoid dependency walk failed
#286
base: main
Are you sure you want to change the base?
Conversation
e2cdfad
to
7a89609
Compare
This does resolve the long-standing issue with |
Very interested, we have been having issues with urllib3 as well |
7a89609
to
42c96c1
Compare
6a992f7
to
9feaa40
Compare
Quality Gate failedFailed conditions |
568bf9f
to
fd8a2de
Compare
fd8a2de
to
ac2addc
Compare
ac2addc
to
9e30454
Compare
9e30454
to
164904a
Compare
164904a
to
34e9f85
Compare
Hey! I'm not sure how this repository works. What would be needed to get this Pull Request going? It would be great to solve the longstanding #183 |
… `dependency walk failed`
34e9f85
to
42f0f17
Compare
Quality Gate failedFailed conditions |
It requires a Poetry release that includes python-poetry/poetry#9427. That will be python-poetry/poetry#9448. |
Resolves: #176
Resolves: #183
Requires: python-poetry/poetry#9427
With python-poetry/poetry#9427 we can fix
dependency walk failed
once and for all. The dependency walker becomes as simple as iterating over a flat list and doing some simple marker operations. There is no complicated erroneous logic anymore because the resulting markers for each locked package can be read from the lock file.I adapted all tests so they are run with an old lock file without markers and with a new lock file with markers and added a test (at the end) that raises
dependency walk failed
for an old lock file and succeeds for a new lock file.