Skip to content

bpo-41933: Clarify wording for s * n in Common Sequence Operations#22570

Merged
JulienPalard merged 2 commits intopython:masterfrom
Sipty:fix-issue-41933
Mar 15, 2021
Merged

bpo-41933: Clarify wording for s * n in Common Sequence Operations#22570
JulienPalard merged 2 commits intopython:masterfrom
Sipty:fix-issue-41933

Conversation

@Sipty
Copy link
Copy Markdown
Contributor

@Sipty Sipty commented Oct 5, 2020

Copy link
Copy Markdown
Contributor

@eamanu eamanu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -0,0 +1 @@
Clarified wording of s * n in the Common Sequence Operations No newline at end of file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think NEWS is not neceesary here. But we need wait for a core dev opinion

@github-actions
Copy link
Copy Markdown

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Dec 20, 2020
Copy link
Copy Markdown
Member

@JulienPalard JulienPalard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer it this way too 👍

@JulienPalard
Copy link
Copy Markdown
Member

Thanks @Sipty !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale Stale PR or inactive for long period of time.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants