Modernize data tutorial to torchvision v2 API

[omkar-334]

Fixes ##3852

Description

Replace deprecated ToTensor() with v2.Compose([v2.ToImage(), v2.ToDtype(torch.float32, scale=True)]) in both the training and test FashionMNIST splits, and switch the import to the v2 namespace.

Checklist

• The issue that is being fixed is referred in the description (see above "Fixes #ISSUE_NUMBER")
• Only one issue is addressed in this pull request
• Labels from the issue that this PR is fixing are added to this pull request
• No unnecessary issues are included into this pull request.

cc @subramen

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3863

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

⏳ No Failures, 2 Pending

As of commit 8710778 with merge base 08435cc ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[sekyondaMeta]

@claude

[claude]

Claude finished @sekyondaMeta's task in 1m 7s —— View job

---

PR Review: Modernize data tutorial to torchvision v2 API

• Gather context and review changes
• Provide review feedback

---

Summary: This is a clean, minimal change that correctly replaces the deprecated ToTensor() with the v2 transforms API. The pattern used (v2.Compose([v2.ToImage(), v2.ToDtype(torch.float32, scale=True)])) is the recommended replacement per the torchvision docs and is consistent with the identical change already merged in PR #3869 for the quickstart tutorial.

Review: LGTM ✅

The changes are correct and well-scoped:

1. Import (line 51): from torchvision.transforms import ToTensor → from torchvision.transforms import v2 — correct namespace switch.
2. Training transform (line 59): ToTensor() → v2.Compose([v2.ToImage(), v2.ToDtype(torch.float32, scale=True)]) — functionally equivalent replacement.
3. Test transform (line 66): Same replacement applied consistently.

No issues found. The change is minimal, addresses only the deprecation, and doesn't introduce unnecessary refactoring.

---