bpo-41933: Clarify wording for s * n in Common Sequence Operations#22570
Merged
Conversation
eamanu
approved these changes
Oct 10, 2020
| @@ -0,0 +1 @@ | |||
| Clarified wording of s * n in the Common Sequence Operations No newline at end of file | |||
Contributor
There was a problem hiding this comment.
I think NEWS is not neceesary here. But we need wait for a core dev opinion
|
This PR is stale because it has been open for 30 days with no activity. |
JulienPalard
approved these changes
Mar 15, 2021
JulienPalard
left a comment
JulienPalard
left a comment
Member
There was a problem hiding this comment.
I prefer it this way too 👍
Member
|
Thanks @Sipty ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://bugs.python.org/issue41933