Pip claims version conflict where there is none; involves extras and VCS deps

[jwodder]

Description

I have a locally-developed package named dandisets-healthstatus. Its all extra contains two dependencies, dandidav @ git+https://github.com/... and dandi (a PyPI package, without any version constraints). dandidav depends on dandi >= 0.58.2. The latest version of dandi on PyPI is 0.59.0.

When I try to do pip install .[all] where the current directory is the source of dandisets-healthstatus, pip fails with:

ERROR: Cannot install dandisets-healthstatus and dandisets-healthstatus[all]==0.0.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    dandisets-healthstatus[all] 0.0.0 depends on dandi; extra == "all"
    dandidav 0.0.0 depends on dandi>=0.58.2

Clearly, dandi and dandi>=0.58.2 should be compatible, yet pip mistakenly thinks otherwise.

The problem also occurs when dandidav and dandi are moved into dandisets-healthstatus's "normal" dependencies instead of making them extras.

I attempted to create an MVCE for this bug using three local, minimal packages whose wheels were provided to pip via --no-index --find-links, but the error did not occur.

Expected behavior

pip install .[all] on the dandisets-healthstatus source code should have successfully installed dandidav and the latest version of dandi.

pip version

23.3.2

Python version

3.11.7

OS

macOS Sonoma 14.2.1

How to Reproduce

1. git clone https://github.com/dandi/dandisets-healthstatus.git (I promise it won't bite)
2. cd dandisets-healthstatus
3. git checkout ea4ebaa6
4. cd code
5. python3 -m venv venv
6. venv/bin/pip install ".[all]"

Output

A log of all output from pip install -vvv can be found at https://gist.github.com/jwodder/cd49394c1dfb2bb1e17a5aa32f5c4a49.

Code of Conduct

• I agree to follow the PSF Code of Conduct.

[jwodder]

Closing in favor of the actual issue: #12484