Fix for pytorch 2.0 compatibility in deepspeed#1
Merged
cbcase merged 1 commit intoaugmentcode:augmentfrom May 12, 2023
Merged
Conversation
marcmac
approved these changes
May 12, 2023
marcmac
left a comment
marcmac
left a comment
There was a problem hiding this comment.
Looks fine. Why do we try to import it in one file, and just assume it won't be there in the other two?
Author
The |
|
I had no idea you could chain import like that. TIL. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From my H100 testing, this was the minimum viable change to deepspeed to work with pytorch 2.
(See deepspeedai@d3de737)