FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

gh-152397: Provide a cross-reference to PEP 798 unpacking syntax by rhettinger · Pull Request #152454 · python/cpython · GitHub

  1. python
  2. cpython

Repository navigation

gh-152397: Provide a cross-reference to PEP 798 unpacking syntax - #152454

Merged
rhettinger merged 1 commit into
python:mainfrom
rhettinger:pep798xref
Jun 27, 2026
ConversationCommits (1)ChecksFiles changed
Merged

gh-152397: Provide a cross-reference to PEP 798 unpacking syntax#152454
rhettinger merged 1 commit into
python:mainfrom
rhettinger:pep798xref

Conversation

rhettinger commented Jun 27, 2026 •
edited by bedevere-app Bot
Loading

Copy link
Copy Markdown
Contributor

rhettinger self-assigned this Jun 27, 2026
rhettinger added the docs Documentation in the Doc dir label Jun 27, 2026
github-project-automation Bot moved this to Todo in Docs PRs Jun 27, 2026

read-the-docs-community Bot commented Jun 27, 2026

Copy link
Copy Markdown

Documentation build overview

📚 cpython-previews | 🛠️ Build #33339473 | 📁 Comparing 0061979 against main (003d362)

  🔍 Preview build  

1 file changed
± library/itertools.html

rhettinger mentioned this pull request Jun 27, 2026
Closed
rhettinger merged commit 8107c53 into python:main Jun 27, 2026
38 checks passed
github-project-automation Bot moved this from Todo to Done in Docs PRs Jun 27, 2026
rhettinger mentioned this pull request Jun 27, 2026
Closed
hugovk changed the title Provide a cross-reference to PEP 798 unpacking syntax gh-152397: Provide a cross-reference to PEP 798 unpacking syntax Jun 27, 2026
hugovk added needs backport to 3.13 only security fixes needs backport to 3.14 bugs and security fixes needs backport to 3.15 bugs and security fixes and removed skip issue labels Jun 27, 2026

miss-islington-app Bot commented Jun 27, 2026

Copy link
Copy Markdown

Thanks @rhettinger for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

miss-islington-app Bot commented Jun 27, 2026

Copy link
Copy Markdown

Thanks @rhettinger for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14.
🐍🍒⛏🤖

miss-islington-app Bot commented Jun 27, 2026

Copy link
Copy Markdown

Thanks @rhettinger for the PR 🌮🎉.. I'm working now to backport this PR to: 3.15.
🐍🍒⛏🤖

bedevere-app Bot commented Jun 27, 2026

Copy link
Copy Markdown

GH-152458 is a backport of this pull request to the 3.13 branch.

bedevere-app Bot removed the needs backport to 3.13 only security fixes label Jun 27, 2026

bedevere-app Bot commented Jun 27, 2026

Copy link
Copy Markdown

GH-152459 is a backport of this pull request to the 3.14 branch.

bedevere-app Bot removed the needs backport to 3.14 bugs and security fixes label Jun 27, 2026

bedevere-app Bot commented Jun 27, 2026

Copy link
Copy Markdown

GH-152460 is a backport of this pull request to the 3.15 branch.

bedevere-app Bot removed the needs backport to 3.15 bugs and security fixes label Jun 27, 2026

rhettinger commented Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

hugovk Thanks for doing the 3.15 backport.

I'm not sure it makes sense for 3.14 and 3.13 though. PEP 798 is a 3.15 feature.

nedbat commented Jun 27, 2026

Copy link
Copy Markdown
Member

Can we change the PEP reference to a link to the syntax description in the docs? And add a "since 3.15" mention?

nedbat commented Jun 27, 2026

Copy link
Copy Markdown
Member

I made a pull request with the change: #152462

rhettinger commented Jun 28, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

My preference is to keep the PEP reference because it best describes the relationship between the new unpacking syntax and the existing itertool functions. Also, the syntax docs in the language reference are rather technical and sometimes difficult to follow. However, if you feel strongly about replacing the PEP reference, I would be happy to make the edit.

I don't feel like the chain docs are the right place for a 3.15 versionadded note. That belongs with the syntax docs and in the PEP. I can't think of other places where versionadded is used in a simple here-are-two-ways-to-do-it code examples. As a reader of the chain docs, I would find a version note to be confusing because chain itself has been stable for decades.

bedevere-app Bot commented Jun 28, 2026

Copy link
Copy Markdown

GH-152460 is a backport of this pull request to the 3.15 branch.

rhettinger added a commit that referenced this pull request Jun 28, 2026
[3.15] gh-152397: Provide a cross-reference to PEP 798 unpacking synt…
26caf56 
…ax (GH-152454) (#152460)

Co-authored-by: Raymond Hettinger <rhettinger@users.noreply.github.com>
Co-authored-by: Rishit Agnihotri <Twix1288@users.noreply.github.com>

nedbat commented Jun 28, 2026

Copy link
Copy Markdown
Member

True, in my pull request I left out the version mention, since the language reference has it. The language reference also has a link to the PEP if people are interested.

The PEP itself starts with:

Important

This PEP is a historical document. The up-to-date, canonical documentation can now be found at Displays for lists, sets and dictionaries, Dictionary displays.

I don't think we should send people outside the docs only for them to find a sign that says they should go back to the docs.

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
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

rhettinger

Labels

docs Documentation in the Doc dir skip news

Projects

Docs PRs
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

Back | FazBrowse Home | New Git URL