bpo-25433: Streamline whitespace documentation#14775
Conversation
Whenever the word "whitespace" was stated more than once within a single section, I added the link to the first one only.
Whenever the word "whitespace" was stated more than once within a single section, I added the link to the first one only.
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Our records indicate we have not received your CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for your contribution, we look forward to reviewing it! |
|
Thank you @rompe for your contribution but could you fix the conflict with |
matrixise
left a comment
There was a problem hiding this comment.
Please, rebase with master and fix the conflicts.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
@rompe, please resolve the merge conflicts. Thanks! |
|
This PR has been languishing while waiting for the merge conflicts to be resolved. I'm going to close this for now to allow someone else to pick it up. If the original author wishes to come back to it, then it can be reopened at that time. Thank you! |
Add a "whitespace" definition to the glossary and link to it from every documentation regarding whitespae.
As requested in bpo-25433, whitespace should be explained only once and all other places should point to this documentation instead of either explaining the term themselves or just stating "whitespace" without an explanation.
No NEWS entry added since this already comes with the code part in #14771 .
https://bugs.python.org/issue25433