Skip to content

Some test dependencies have no lower bounds #42989

@potiuk

Description

@potiuk

Some test dependencies have no "lower bounds" - this is not very good because "lowest-direct" dependency resolution might run much longer. Currently when uv is making the resolution, it prints warnings

  • warning: Missing version constraint (e.g., a lower bound) for asgiref
  • warning: Missing version constraint (e.g., a lower bound) for requests-toolbelt
  • warning: Missing version constraint (e.g., a lower bound) for cloudpickle
  • warning: Missing version constraint (e.g., a lower bound) for python-ldap
  • warning: Missing version constraint (e.g., a lower bound) for plyvel
  • warning: Missing version constraint (e.g., a lower bound) for opentelemetry-exporter-prometheus
  • warning: Missing version constraint (e.g., a lower bound) for amqp
  • warning: Missing version constraint (e.g., a lower bound) for virtualenv
  • warning: Missing version constraint (e.g., a lower bound) for types-markdown
  • warning: Missing version constraint (e.g., a lower bound) for types-deprecated
  • warning: Missing version constraint (e.g., a lower bound) for types-pymysql
  • warning: Missing version constraint (e.g., a lower bound) for types-pyyaml
  • warning: Missing version constraint (e.g., a lower bound) for types-aiofiles
  • warning: Missing version constraint (e.g., a lower bound) for types-certifi
  • warning: Missing version constraint (e.g., a lower bound) for types-croniter
  • warning: Missing version constraint (e.g., a lower bound) for types-docutils
  • warning: Missing version constraint (e.g., a lower bound) for types-paramiko
  • warning: Missing version constraint (e.g., a lower bound) for types-protobuf
  • warning: Missing version constraint (e.g., a lower bound) for types-python-dateutil
  • warning: Missing version constraint (e.g., a lower bound) for types-python-slugify
  • warning: Missing version constraint (e.g., a lower bound) for types-pytz
  • warning: Missing version constraint (e.g., a lower bound) for types-redis
  • warning: Missing version constraint (e.g., a lower bound) for types-requests
  • warning: Missing version constraint (e.g., a lower bound) for types-setuptools
  • warning: Missing version constraint (e.g., a lower bound) for types-tabulate
  • warning: Missing version constraint (e.g., a lower bound) for types-termcolor
  • warning: Missing version constraint (e.g., a lower bound) for types-toml
  • warning: Missing version constraint (e.g., a lower bound) for ipykernel
  • warning: Missing version constraint (e.g., a lower bound) for pywinrm
  • warning: Missing version constraint (e.g., a lower bound) for scrapbook

We should make sure that all those dependencies have reasonable lower-bounds . Ideally versions that are not too old (6 months?). We shoudl look at them individually though, to see if there might be potential issues when we are choosing the lower bounds.

Metadata

Metadata

Assignees

Labels

area:dependenciesIssues related to dependencies problems

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions