10000 2.3.0 not backward compatible with torchdata · Issue #124907 · pytorch/pytorch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

2.3.0 not backward compatible with torchdata #124907

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.

Sign up for GitHub

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

Jump to bottom
Closed
npuichigo opened this issue Apr 25, 2024 · 5 comments
8000
Closed

2.3.0 not backward compatible with torchdata #124907

npuichigo opened this issue Apr 25, 2024 · 5 comments
Labels
module: binaries Anything related to official binaries that we release to users module: regression It used to work, and now it doesn't triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone
2.3.1

Comments

@npuichigo
Copy link
npuichigo commented Apr 25, 2024 •
edited by pytorch-bot bot
Loading

🐛 Describe the bug

f428183 fixing not included in 2.3.0 release

Versions

pytorch 2.3.0

cc @seemethere @malfet @osalpekar @atalman
@malfet malfet added this to the 2.3.1 milestone Apr 25, 2024
@malfet malfet added module: binaries Anything related to official binaries that we release to users module: regression It used to work, and now it doesn't triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Apr 25, 2024
@malfet
Copy link
Contributor
malfet commented Apr 25, 2024

Thank you for reporting. Will probably cherry-pick the change into 2.3.1, but please note, that per https://github.com/pytorch/data/blob/main/README.md#torchdata-see-note-below-on-current-status torchdata has not been actively maintained, so if one needs to use torchdata they probably have to stick to older PyTorch versions

@mfbalin mfbalin mentioned this issue Apr 27, 2024
Closed
@npuichigo
Copy link
Author

@malfet So is here any further plan to replace torchdata?

@mfbalin mfbalin mentioned this issue May 9, 2024
Merged
8 tasks
@mfbalin
Copy link
mfbalin commented May 9, 2024

Thank you for reporting. Will probably cherry-pick the change into 2.3.1, but please note, that per https://github.com/pytorch/data/blob/main/README.md#torchdata-see-note-below-on-current-status torchdata has not been actively maintained, so if one needs to use torchdata they probably have to stick to older PyTorch versions

Is this commit going to be cherry picked for 2.3.1?

@atalman atalman mentioned this issue May 13, 2024
Closed
@atalman
Copy link
Contributor
atalman commented May 13, 2024

Closing this since #122616 fixes it in nightly and cherry-pick submitted for 2.3.1

@atalman atalman closed this as completed May 13, 2024
This was referenced May 22, 2024
Open
Closed
@atalman
Copy link
Contributor
atalman commented May 31, 2024

Validated with 2.3.1:

Python 3.10.14 (main, May  6 2024, 19:42:50) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch, torchdata
>>> print(torch.__version__)
2.3.1
>>> print(torchdata.__version__)
0.7.1
>>>

@mfbalin mfbalin mentioned this issue May 31, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
module: binaries Anything related to official binaries that we release to users module: regression It used to work, and now it doesn't triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Milestone
2.3.1
Development

No branches or pull requests
4 participants
@malfet @atalman @npuichigo @mfbalin
0