Changed from hardcoded http codes to using constants from httplib
Review Request #7625 — Created Sept. 13, 2015 and submitted
Changed from hardcoded 304 and 401 http codes to using the NOT_MODIFIED and UNAUTHORIZED constants from httplib for better readability.
RBTools nose test results - all passed fine
Ran 166 tests in 3.966s
OK (SKIP=50)
Description | From | Last Updated |
---|---|---|
Col: 80 E501 line too long (113 > 79 characters) |
reviewbot | |
Col: 25 E127 continuation line over-indented for visual indent |
reviewbot | |
I think we want to keep 200 and 300 as numbers, and only use the symbolic error for NOT_MODIFIED. |
david | |
Don't add this line (io and json are still standard-library modules). |
david |
-
Tool: Pyflakes Processed Files: rbtools/api/request.py Tool: PEP8 Style Checker Processed Files: rbtools/api/request.py
-
Tool: Pyflakes Processed Files: rbtools/api/transport/sync.py rbtools/api/request.py rbtools/commands/__init__.py Tool: PEP8 Style Checker Processed Files: rbtools/api/transport/sync.py rbtools/api/request.py rbtools/commands/__init__.py
-
Tool: Pyflakes Processed Files: rbtools/api/request.py Tool: PEP8 Style Checker Processed Files: rbtools/api/request.py
-
Tool: Pyflakes Processed Files: rbtools/api/request.py Tool: PEP8 Style Checker Processed Files: rbtools/api/request.py
-
Tool: Pyflakes Processed Files: rbtools/api/request.py Tool: PEP8 Style Checker Processed Files: rbtools/api/request.py
- Groups:
-
Make sure to follow our guide on choosing a good summary and description: https://www.reviewboard.org/docs/codebase/dev/writing-good-descriptions/
Your summary should never mention bug numbers (those will be provided automatically in the description when the change lands), and your descriptions should explain the why and how.
-
Looks good.
Also, regarding the description, it's always good to run tests for every change, no matter what :)
-
Hey Anthony, would you mind running the tests with this patch to ensure all is well, and then posting the results in Testing Done?