gh-62897: Update PyUnicode parameter names#12680
gh-62897: Update PyUnicode parameter names#12680serhiy-storchaka merged 10 commits intopython:mainfrom
Conversation
serhiy-storchaka
left a comment
There was a problem hiding this comment.
Do not change C sources. Update only the documentation. Don't forget to update the text following the signature.
|
Alright, I'll revert the code changes. Phrasing and discussion on the issue made me think it also wanted the code names unified with the doc names |
matrixise
left a comment
There was a problem hiding this comment.
Thank you for your contribution, but could you check your PR, because you change some parameters, but the documentation is not updated with these new names.
|
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 And if you don't make the requested changes, you will be put in the comfy chair! |
|
Not sure why there's an error about seeing |
|
@CraftSpider, in order to move issues along once changes have been made, this repo uses bots. Please take a look at this message for more info about that. Please also resolve the merge conflict before adding that comment requesting further review. Thanks! |
Function descriptions should now all match the changed parameters of their functions
945760d to
f69fad4
Compare
|
I have made the requested changes; please review again Thank you for the patience, I got into other projects and basically forgot about this for a while |
|
Thanks for making the requested changes! @matrixise: please review the changes made to this pull request. |
|
Fixed a merge error caused by other changes since this was made, @matrixise can you please review this when you have time? |
|
Could anyone help to sort out the new |
|
Thanks @CraftSpider for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
Thanks @CraftSpider for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
|
Sorry, @CraftSpider and @serhiy-storchaka, I could not cleanly backport this to |
|
Sorry, @CraftSpider and @serhiy-storchaka, I could not cleanly backport this to |
|
GH-112744 is a backport of this pull request to the 3.12 branch. |
…GH-12680) Standardize PyUnicode C API parameter names across the documentation. (cherry picked from commit b31232d) Co-authored-by: Rune Tynan <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
…GH-12680) Standardize PyUnicode C API parameter names across the documentation. (cherry picked from commit b31232d) Co-authored-by: Rune Tynan <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
|
GH-112745 is a backport of this pull request to the 3.11 branch. |
…H-112744) Standardize PyUnicode C API parameter names across the documentation. (cherry picked from commit b31232d) Co-authored-by: Rune Tynan <[email protected]>
…H-112745) Standardize PyUnicode C API parameter names across the documentation. (cherry picked from commit b31232d) Co-authored-by: Rune Tynan <[email protected]>
Standardize PyUnicode C API parameter names across the documentation. Co-authored-by: Serhiy Storchaka <[email protected]>
Standardize PyUnicode C API parameter names across the documentation. Co-authored-by: Serhiy Storchaka <[email protected]>
Per the linked issue, PyUnicode functions/methods had many different parameter names, this PR aims to unify them. There is still at least one unanswered question on the bug-tracker, but it seemed a good idea to get a PR of the existing fixes started to solicit active comments.
https://bugs.python.org/issue18697