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
Add docstrings to fields of urllib.parse results #70008
Comments
I can help with this. Should I propose the changes I am going to make before making them or just create the patch? |
Here is the patch, please review it. Do I need to write any test? |
Thanks, Swati. I left a few comments on Rietveld: http://bugs.python.org/review/25822/ A test wouldn't hurt, but you can wait for further review comments to avoid updating tests each time you get a comment. |
[padding] I wonder if the doc strings are too specific when they mention “request”, “file”, “download”, “page”, etc. Maybe these could just be examples of what the fields are used for (e.g. “The hierarchical path, such as the path to a file to download”). Or maybe they could be changed to general terms, but this may be hard. Also, some of them seem redundant. Does it really add anything to say the “query” field is “the query parameter”? |
I wouldn't normally write a test for a docstring patch. |
Could you please also add docstrings for _DefragResultBase? I agree that there is no need to write tests. |
New changeset 7bfcb8b75ad9 by Senthil Kumaran in branch 'default': |
Thank you, Swati. I reviewed and committed your patch. I had to make some minor formatting changes while keeping an eye for the maintainability of the module and doc strings.
Thanks for addressing the review comments from other developers. |
Thank you Senthil for the improvements, I'll try to make it better next time :) |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: