We are excited to announce the release of PyTorch® 2.5. All the binaries published to PyPI, Anaconda, and download.pytorch.org . Installation instructions for the new release can be found at the familiar getting started page .
The release notes for PyTorch and Domain Libraries can be found on following links:
I understand that every release involves prioritizing various issues, but I’m curious about the timeline for addressing this particular bug. Is it reasonable to expect a fix in version 2.5.1?
Given that this regression was known before the release, I believe it would have been helpful to have this information communicated in the release notes.
@hassonofer I see the issue was created in August. For the solution to get into 2.5.1, there needs to be a pull request first. If you have an idea what to do, proposing a fixing pull request will speed up things.
Separately, I will bring this issue to the attention of the core PyTorch developers.
@hassonofer Good news, the issue should be fixed in the upcoming 2.5.1
You can try the release candidate pip3 install torch==2.5.1 --index-url https://download.pytorch.org/whl/test/cu124