-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Temporary fix to be BC compatible with torchtext #6168
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6168 +/- ##
========================================
- Coverage 91% 46% -45%
========================================
Files 160 160
Lines 11435 11323 -112
========================================
- Hits 10446 5260 -5186
- Misses 989 6063 +5074 |
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.
Until PyTorch Lightning can use the new API
What's blocking it?
Can you look at the failing tests?
It seems the CI VMs are using older
|
it is expected, see min requirements |
seems to be duplicate to #6211 |
… pull down 1.8.0. Lightning-AI/pytorch-lightning#6168 Signed-off-by: Tibor Kiss <kiss.tibor@gmail.com>
… pull down 1.8.0. Lightning-AI/pytorch-lightning#6168 Signed-off-by: Tibor Kiss <kiss.tibor@gmail.com>
… pull down 1.8.0. Lightning-AI/pytorch-lightning#6168 Signed-off-by: Tibor Kiss <kiss.tibor@gmail.com>
What does this PR do?
torchtext.data.Batch
was deprecated (and moved totorchtext.legacy.data.Batch
, which breaks PyTorch LightningUntil PyTorch Lightning can use the new API, it should use the legacy version to allow PyTorch nightly (torch, torchtext) users to keep using PyTorch lightning during development
Fixes #6165