-
Notifications
You must be signed in to change notification settings - Fork 286
Description
❌ 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 --seed to create virtualenvs. The --seed parameter adds in pip and setuptools, but usually the most recent versions. This uncovered that the latest version of pip has an issue with pip-tools, so running pip-compile requirements.in will fail.
Additionally, pip and pip-tools have been having recurring conflicts which cause friction. We might consider wholly adopting the uv approach, and drop pip-tools
Errors and logs
AttributeError: 'InstallRequirement' object has no attribute 'use_pep517'
# or
AttributeError: 'PackageFinder' object has no attribute 'allow_all_prereleases'
Expected behavior
We're able to compile our dependency files-- pip and pip-tools are 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
- Run
uv venv --seedto create virtualenv - Install all packages
- Attempt to run
pip-compile requirements.in
