Skip to content
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

How does pipx resolve conflicting subdependencies when using inject option #1577

Open
maxkoretskyi opened this issue Nov 14, 2024 · 0 comments

Comments

@maxkoretskyi
Copy link

maxkoretskyi commented Nov 14, 2024

Suppose I have a library kywy v1 that defines the dependency on numpy==1.26.4. Then I have a kywy-server app v5 that depends on kywy==1 and the matching numpy==1.26.4. When I

pipx install kywy-server==5

all is good and I can run $ kywy-server.

Now, I update the kywy version to v2 and change the dependency to numpy==2.1.3. It's now different to numpy==1.26.4 used by kywy-server. Then I want to inject this new kywy v2 into the kywy-server:

pipx inject kywy-server kywy==2

which would result into a collition of subdependencies: kywy==2 requires numpy==2.1.3, but kywy-server==5 which hasn't changed still requires numpy==1.26.4. Pip would result into a subdeps conflict and won't resolve this automatically.

I'm wondering how pipx handles it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant