-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Pipenv does not follow URL-based subdependencies of a URL-based dependency #3964
Comments
I have the same issue, three packages in a chain dependency fasion.. wrote about it here yesterday but I guess this is a better place, will copy paste it here |
Hi @zicvic @selik |
Hi! Have any of you looked into where this would resolve in the code and have an idea for how to fix this? I'm a little bit tied up for the coming three weeks but after that I could take a look and see if I can come up with a solution since it doesn't seem to be anyone working on this at the moment. |
@zicvic You might want to check out how Pip solved it in pypa/pip#5571 |
I'm getting bitten by this, too. Is there any known workaround? |
I ended up launching my own private pypi server and publishing to it so I could stop using url references |
I'm having the issue with just one level, I have a pip module (fbn-googleapi) on our own pypi server, and in that module's setup.py it has the req:
instead of an editable link to the github repo. I have to add |
this is definitely still broken in my scenario, just tried with 2021.11.23 |
I have three projects. Project A depends on B, which in turn depends on C. Each is private, hosted in GitHub. Project A in its
Pipfile
specifies its dependency on B via URLB = {editable = true,git = "ssh://git@github.com/selik/B.git"}
. Project B specifies its dependency on C in itssetup.cfg
file using PEP-508 standard for URL-based dependenciesC @ git+ssh://git@github.com/selik/C.git#egg=C
.Unfortunately, the real name I chose for Project C happens to collide with a project listed on PyPI. When Pipenv installs all of Project A's dependencies, I get the PyPI project C instead of my personal project C.
I can work around this by listing my personal project C as a direct dependency of project A. This is frustrating, because of the difficulty diagnosing the issue and the increased maintenance burden for anything which depends on Project B.
It looks like this feature was merged into Pip with pypa/pip#5571 in July 2018, but I'm not sure from the conversation in that thread.
The text was updated successfully, but these errors were encountered: