Skip to content

requests is pinned to a specific version, rather than setting a range of versions  #466

Open
@FlorianRhiem

Description

@FlorianRhiem

Describe the bug
Flask-MonitoringDashboard has fixed the requests version to exactly 2.32.0 in the current requirements.txt and to exactly 2.31.0 in the current release. This causes a conflict with another package requiring at least 2.32.3.

This could be fixed by requiring at least 2.32.0 rather than pinning requests to that version, e.g. by using something like requests>=2.32.0,<3.0.0.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new venv (python3 -m venv venv)
  2. Try to install both Flask-MonitoringDashboard 3.3.2 and roc-validator (venv/bin/pip install Flask-MonitoringDashboard==3.3.2 roc-validator==0.4.6)

Expected behavior
It should be possible to install the latest version of Flask-MonitoringDashboard along with packages requiring a minimum version of requirements that is greater than 2.32.0 or 2.31.0.

Output

ERROR: Cannot install flask-monitoringdashboard==3.3.2 and roc-validator==0.4.6 because these package versions have conflicting dependencies.

The conflict is caused by:
    flask-monitoringdashboard 3.3.2 depends on requests==2.31.0
    roc-validator 0.4.6 depends on requests<3.0.0 and >=2.32.3

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

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

Desktop:

  • macOS 15.1
  • Python 3.13.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions