-
Notifications
You must be signed in to change notification settings - Fork 65
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
Initial download is extremely slow and times out in IDLE #57
Comments
Thanks for letting me know. I think this is the related issue: https://stackoverflow.com/questions/35895864/what-is-the-difference-between-cmd-and-idle-when-using-tqdm/35900117#35900117 |
But that's just about the progress bar. The command shouldn't fail. @Pikamander2 can you post the error message if there is one? |
@jxmorris12 - Just tested it on a different setup (Windows 7 + IDLE 3.8.9 whereas last time I used Windows 10 + IDLE 3.9.0) and the exact same thing happened. The download rate starts out at a reasonable value but then rapidly deteriorates down to a few KB/s and eventually just a few bytes per second. After about 10-20 minutes, it finally fails with a zipfile.BadZipFile error:
Screenshots of the gradually slowing download rate and messy output: https://imgur.com/a/e5uK0YQ Here's the code I used:
The issue should be reproducible on any Windows + IDLE setup in which the LanguageTool files have not yet been downloaded. |
When run in IDLE for the first time (at least on Windows), the tool floods the IDLE shell with thousands of download progress messages and gradually grind to a halt until it reaches several bytes per second and eventually fails.
It works flawlessly in cmd/terminal, but it would be nice if it worked correctly in IDLE as well. I realize that IDLE has a lot of issues and may or may not be worth fully supporting, but currently there's not even any indication to the user about what the problem is.
The text was updated successfully, but these errors were encountered: