-
-
Notifications
You must be signed in to change notification settings - Fork 307
pip-tools v7.5.2 is incompatible with pip>=26 #5698
Copy link
Copy link
Labels
DEV: dev-opsP0 - criticalPriority: Release blocker or regressionPriority: Release blocker or regressionTAG: dependenciesTAG: dev experiencedependenciesPull requests that update a dependency filePull requests that update a dependency file
Description
Activity
Metadata
Metadata
Assignees
Labels
DEV: dev-opsP0 - criticalPriority: Release blocker or regressionPriority: Release blocker or regressionTAG: dependenciesTAG: dev experiencedependenciesPull requests that update a dependency filePull requests that update a dependency file
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Observed behavior
I've been using
uv venv --seedto create virtualenvs. The--seedparameter adds inpipandsetuptools, but usually the most recent versions. This uncovered that the latest version ofpiphas an issue withpip-tools, so runningpip-compile requirements.inwill fail.Additionally,
pipandpip-toolshave been having recurring conflicts which cause friction. We might consider wholly adopting theuvapproach, and droppip-toolsErrors and logs
Expected behavior
We're able to compile our dependency files--
pipandpip-toolsare compatible.User-facing consequences
Developers may encounter this and not understand what's wrong. The recurring issues with these packages cause us headaches.
Steps to reproduce
uv venv --seedto create virtualenvpip-compile requirements.in