-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Drop support for PyTorch 1.10 #16492
Conversation
for more information, see https://pre-commit.ci
⛈️ Required checks status: Has failure 🔴
Groups summary🟢 pytorch_lightning: Tests workflow
These checks are required after the changes to 🟢 pytorch_lightning: Azure GPU
These checks are required after the changes to 🟢 pytorch_lightning: Benchmarks
These checks are required after the changes to 🟢 pytorch_lightning: Azure HPU
These checks are required after the changes to 🟢 pytorch_lightning: Azure IPU
These checks are required after the changes to 🟢 pytorch_lightning: Docs
These checks are required after the changes to 🟢 pytorch_lightning: Docker
These checks are required after the changes to 🟢 lightning_fabric: CPU workflow
These checks are required after the changes to 🟢 lightning_fabric: Azure GPU
These checks are required after the changes to 🟢 mypy
These checks are required after the changes to 🟢 installThese checks are required after the changes to 🔴 link-check
These checks are required after the changes to Thank you for your contribution! 💜
|
This reverts commit 9618f73.
What does this PR do?
Keeping our version compatibility window, our 2.0 will support (1.11, 1.12, 1.13, 2.0)
Does your PR introduce any breaking changes? If yes, please list them.
Removes PyTorch 1.10 support
cc @carmocca @akihironitta @Borda @justusschock @awaelchli