-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Fix var name issue #753
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
Fix var name issue #753
Conversation
|
Is there a way to add a test for the "chunked" case? Line 177 and 178 can be removed, and there are a bunch of unused imports in this file (a plug for IntelliJ-- it points out unused variables and imports, including the typo you are fixing). |
|
i.e., the blank line and the comment? isn't cleaning up a different PR altogether? |
|
I think removing unused local variables and unused imports can be part of this PR. But if you want to do it as a second one, that's fine. I am speaking about these lines-- Definitely would like to see a test that hits the chunking, if feasible. |
|
A couple other questions--
|
|
Moving to PR against release |
…ebug-view add a debug_request view that prints the request.
updated polls xblock version on mcka
Unfork help modal
…-attempts-fix Proversity/problem attempts fix
#753) This doesn't make metrics-sending *work* under 3.5 (capture_output isn't supported on that version, for instance) but it does prevent the presence of the script from breaking instrumented make targets. As long as the script loads and the main method runs properly under 3.5, try/else blocks can handle any other incompatibilities. Some people still use Python 3.5 with devstack, possibly by accident, even though devstack is supposed to be on 3.8 now. Much of devstack works with 3.5, even if requirements can no longer be installed, so someone who has docker-compose installed externally and doesn't use a virtualenv may not notice the environment mismatch. While we'd like people to upgrade to 3.8, the metrics script should at least not break their workflow in the meantime, since it is optional. Also: Note python 3.8 requirement in README while I'm at it.
Wrong var name causes django-chunked (> 10MB?) asset upload to fail.