Skip to content

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

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.

Sign up for GitHub

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

Merged
JulienPalard merged 2 commits into from
Mar 15, 2021
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7385cd7
bpo-41933: Clarify wording for s * n in Common Sequence Operations
lookHack01 Oct 5, 2020
1644ca1
📜🤖 Added by blurb_it.
blurb-it[bot] Oct 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Lib/pydoc_data/topics.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12904,9 +12904,9 @@
'| "s + t" | the concatenation of *s* and *t* '
'| (6)(7) |\n'
'+----------------------------+----------------------------------+------------+\n'
'| "s * n" or "n * s" | equivalent to adding *s* to '
'| "s * n" or "n * s" | equivalent to *n* copies of the '
'| (2)(7) |\n'
'| | itself *n* times '
'| | *s* sequence '
'| |\n'
'+----------------------------+----------------------------------+------------+\n'
'| "s[i]" | *i*th item of *s*, origin 0 '
Expand Down
1 change: 1 addition & 0 deletions Misc/NEWS.d/next/Documentation/2020-10-05-20-04-43.bpo-41933.Pff94-.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarified wording of s * n in the Common Sequence Operations
Copy link
Contributor

@eamanu eamanu Oct 10, 2020

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