-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Update checkpoint warning to target PyTorch 2.9 #160725
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/160725
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 60dbdb1 with merge base eaa5d9d ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
The committers listed above are authorized under a signed CLA. |
@pytorchbot label "topic: not user facing" |
hi @soulitzer, you've reviewed related issue, maybe you can check this PR too! |
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.
Thanks!
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Follow-up to pytorch#160534. Fixes the docstrings and the warning in checkpoint_sequential, which presumably should have same deprecation notice Pull Request resolved: pytorch#160725 Approved by: https://github.com/soulitzer
Follow-up to #160534. Fixes the docstrings and the warning in checkpoint_sequential, which presumably should have same deprecation notice