Skip to content

Pipenv does not follow URL-based subdependencies of a URL-based dependency #3964

@selik

Description

@selik

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 URL B = {editable = true,git = "ssh://git@github.com/selik/B.git"}. Project B specifies its dependency on C in its setup.cfg file using PEP-508 standard for URL-based dependencies C @ 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions