[Python] ResolutionImpossible from pip despite no apparent version conflict

Discussão em 'Python' iniciado por Stack, Junho 27, 2025.

  1. Stack

    Stack Membro Participativo

    Sometimes pip complains of conflicting dependencies despite there being no actual version conflict, for example in this case even after removing the specific version of elastic-apm from constraints.txt entirely (just leaving it in mypackage's setup.py) it still failed as follows:

    ERROR: Cannot install elastic-apm because these package versions have conflicting dependencies.

    The conflict is caused by:
    mypackage 1.2.3 depends on elastic-apm
    The user requested (constraint) elastic-apm

    To fix this you could try to:
    1. loosen the range of package versions you've specified
    2. remove package versions to allow pip attempt to solve the dependency conflict

    ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts


    This was with pip 22.1.2 & python 3.10 using a command like this (i.e. use a local folder of wheels, not PyPI)

    pip install -r requirements.txt -c constraints.txt --no-index --find-links LOCALDIR --no-cache-dir --isolated


    Why is pip complaining about conflicting dependencies when there are in fact no specific versions or ranges requested at all, never mind conflicting ones?

    Continue reading...

Compartilhe esta Página