-
-
Notifications
You must be signed in to change notification settings - Fork 2k
fix: update torch version requirement and Python 3.11 doc references #2313
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -78,10 +78,10 @@ retry==0.9.2 | |
| sentence-transformers==5.3.0 | ||
| sqlalchemy>=2.0,<3 | ||
| tiktoken==0.12.0 | ||
| tokenizers==0.22.2 | ||
| torch==2.11.0 | ||
| tqdm==4.67.3 | ||
| transformers==5.4.0 | ||
| tokenizers==0.22.1 | ||
| torch>=2.2.0 | ||
| tqdm==4.67.1 | ||
| transformers==4.57.3 | ||
|
Comment on lines
+81
to
+84
|
||
| typing-extensions==4.15.0 | ||
| typing-inspect==0.9.0 | ||
| tzdata==2025.3 | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using an unbounded lower pin for torch (torch>=2.2.0) can allow a future major release to be installed, potentially breaking runtime compatibility. Other dependencies here frequently include an upper bound when using a range (e.g., sqlalchemy>=2.0,<3), so consider adding an upper cap for torch as well (for example, <3) to reduce install-time surprises.