Skip to content

What's New in Python 3.16 (copyediting) #151914

Open

Activity

  1. added
    docsDocumentation in the Doc dir
    3.16new features, bugs and security fixes
    on Jun 22, 2026
  2. added a commit that references this issue on Jun 22, 2026
  3. added a commit that references this issue on Jul 5, 2026
  4. added a commit that references this issue on Jul 10, 2026
  5. added a commit that references this issue on Aug 30, 2026
  6. LeonxLJX commented on Sep 3, 2026

    @LeonxLJX

    I'd like to take this one.

    Reading the issue, this looks like a documentation-clarity gap rather than a code defect: the current page doesn't give readers enough to self-diagnose, which is why it surfaces here as an issue instead of being answered by the docs.

    Plan: locate the relevant section, confirm what the code actually does today (so the docs match behavior, not intent), tighten the wording, and scan neighboring pages for the same inconsistency — otherwise the fix just relocates the confusion.

    One thing to confirm before writing: minimal correction scoped to this page, or also cross-link from related guides if the same gap shows up there?

    (claiming via @LeonxLJX)

  7. hugovk commented on Sep 3, 2026

    @hugovk
    MemberAuthor

    @LeonxLJX Please don't post LLM output without reading it or this issue.

    See https://devguide.python.org/getting-started/ai-tools/

  8. added a commit that references this issue on Sep 12, 2026
  9. added 2 commits that reference this issue on Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.16new features, bugs and security fixesdocsDocumentation in the Doc dir

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions