Cleanup datapipes #1332
Open
Cleanup datapipes #1332
Conversation
This file contains 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
facebook-github-bot
added
the
CLA Signed
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/data/1332
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 7399cce with merge base 6b762ba ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
andrewkho
changed the base branch from
andrewkh/cleanup-datapipes-dlv2
to
main
|
@andrewkho has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@andrewkho has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There is some code here that we may want to bring back at some point, eg tfrecord, aistore, and potentially others. But we can always go back to tagged 0.9.0 release and bring back as necessary instead of starting with too much