IWSLT2017 Download Issue in torchtext v0.11.0
See original GitHub issueDownloaling IWSLT2017 raises Internal Error. This is the error message:
RuntimeError: Internal error: confirm_token was not found in Google drive link.
I tried to use both the function and module version, but both raise the same error:
train_iter, valid_iter, test_iter = torchtext.datasets.IWSLT2017()
train_iter, valid_iter, test_iter = torchtext.datasets.iwslt2017.IWSLT2017()
Please have a look and fix it as soon as possible.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
torchtext 0.11.0 - PyPI
In the v0.9.0 release, we moved the following legacy code to torchtext.legacy. This is part of the work to revamp the torchtext library...
Read more >torchtext legacy - You.com | The AI Search Engine You Control
I am trying to use torchtext to process test data, however, I get the error: "AttributeError: module 'torchtext' has no attribute 'legacy'", when...
Read more >Torchtext 0.13.0 documentation - PyTorch
This library is part of the PyTorch project. PyTorch is an open source machine learning framework. Features described in this documentation are classified...
Read more >Data Loaders and Abstractions for Text and NLP - Morioh
Note: The legacy code discussed in torchtext v0.7.0 release note has been retired to ... pip install spacy python -m spacy download en_core_web_sm....
Read more >torchtext Changelog - pyup.io
Fix OBO error for vocab files with empty lines (1841) ... IWSLT2017 (1547) ... release notes](https://github.com/pytorch/text/releases/tag/v0.11.0-rc3).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Nayef211 yes looks like it’s resolved now, thanks.
@austinvhuang were you able to verify if updating to version
0.12.0
resolved your issue?