Skip to content

fix: normalize torch version to >=2.1.0 across all dependency files#37

Open
spoturno wants to merge 1 commit intokyegomez:mainfrom
spoturno:fix/torch-version-consistency
Open

fix: normalize torch version to >=2.1.0 across all dependency files#37
spoturno wants to merge 1 commit intokyegomez:mainfrom
spoturno:fix/torch-version-consistency

Conversation

@spoturno
Copy link
Copy Markdown

Problem

The torch version requirement is inconsistent across the three dependency files:

File Was
pyproject.toml torch = "2.11.0" (exact pin to a non-existent version)
requirements.txt torch>=2.1.0
training/requirements.txt torch>=2.11.0 (also non-existent)

torch 2.11.0 does not exist on PyPI — the latest 2.x releases follow 2.1.x, 2.2.x, 2.3.x, etc. This causes install failures for anyone using pyproject.toml or the training requirements.

Fix

Aligned all three files to torch>=2.1.0, matching the existing requirements.txt convention.

pyproject.toml pinned torch==2.11.0 (an invalid version), requirements.txt
used >=2.1.0, and training/requirements.txt used >=2.11.0. Aligned all
three to >=2.1.0 for consistency.
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

Successfully merging this pull request may close these issues.

1 participant