Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bitsandbytes forces non-dev version of PyTorch #1490

Closed
t-vi opened this issue Jan 24, 2025 · 0 comments
Closed

bitsandbytes forces non-dev version of PyTorch #1490

t-vi opened this issue Jan 24, 2025 · 0 comments

Comments

@t-vi
Copy link

t-vi commented Jan 24, 2025

System Info

When I have a dev version of PyTorch installed, the ~=2.0 dependency appears to cause PyTorch to be downgraded, which might not be intended. Quite likely >=2.0<3 would work better.

From an installation log:

Requirement already satisfied: torch~=2.0 in /opt/hostedtoolcache/Python/3.10.16/x64/lib/python3.10/site-packages (from bitsandbytes==0.45.1->-r requirements/test.txt (line 20)) (2.7.0.dev20250124+cpu)
Collecting torch~=2.0 (from bitsandbytes==0.45.1->-r requirements/test.txt (line 20))
  Downloading torch-2.5.1-cp310-cp310-manylinux1_x86_64.whl.metadata (28 kB)

I should say that it's not necessarily unreasonable to expect ~= to keep 2.7.0.dev... as a dependency but apparently, it does not.

Reproduction

To reproduce install nightly, e.g.

pip3 install --pre torch torchvision torchaudio --index-url https://download.pytorch.org/whl/nightly/cu124

and then bitsandbytes.

Expected behavior

keep the installed version of PyTorch

matthewdouglas added a commit that referenced this issue Jan 28, 2025
matthewdouglas added a commit that referenced this issue Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant