GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — datetime.isoformat() docstring has a typo · Issue #135956 · python/cpython

datetime.isoformat() docstring has a typo #135956

New issue
Copy link
New issue
Copy link
Closed
Closed
datetime.isoformat() docstring has a typo#135956
Copy link
Labels
docsDocumentation in the Doc dirDocumentation in the Doc dir

Description

@jason-mcgowan
jason-mcgowan
opened on Jun 25, 2025
Issue body actions

Documentation

In 3.13 cpython/Lib/_pydatetime.py line 2046-2047, linked below, the docstring has a typo. It repeats the word "giving".

cpython/Lib/_pydatetime.py

Lines 2046 to 2047 in c148a68

If self.tzinfo is not None, the UTC offset is also attached, giving
giving a full format of 'YYYY-MM-DD HH:MM:SS.mmmmmm+HH:MM'.

Linked PRs

  • gh-135956: Remove duplicate word in _pydatetime docstring #135957
  • [3.14] gh-135956: Remove duplicate word in _pydatetime docstring (GH-135957) #135962
  • [3.13] gh-135956: Remove duplicate word in _pydatetime docstring (GH-135957) #135963

Activity

  1. jason-mcgowan
    added
    docsDocumentation in the Doc dirDocumentation in the Doc dir
    on Jun 25, 2025
  2. github-project-automation
    added this to docs issueson Jun 25, 2025
  3. github-project-automation
    moved this to Todo in docs issueson Jun 25, 2025
  4. terryjreedy commented on Jun 25, 2025

    @terryjreedy
    terryjreedy
    on Jun 25, 2025
    Member
    More actions

    Still in main. Preparing PR.

  5. terryjreedy
    added 2 commits that reference this issue on Jun 25, 2025

    pythongh-135956: Remove duplicate word in _pydatetime docstring

    087c263

    pythongh-135956: Remove duplicate word in _pydatetime docstring

    76a4195
  6. brianschubert commented on Jun 25, 2025

    @brianschubert
    brianschubert
    on Jun 25, 2025
    Contributor
    More actions

    A quick regex search for \b(\w+)\b *\n *\1\b shows that this is the only such case in Lib/ public docstrings

  7. terryjreedy
    added a commit that references this issue on Jun 26, 2025

    gh-135956: Remove duplicate word in _pydatetime docstring (#135957)

    e3ea6f2
  8. miss-islington
    added 2 commits that reference this issue on Jun 26, 2025

    pythongh-135956: Remove duplicate word in _pydatetime docstring (pyth…

    9115792

    pythongh-135956: Remove duplicate word in _pydatetime docstring (pyth…

    406dbf2
  9. terryjreedy
    added 2 commits that reference this issue on Jun 26, 2025

    [3.13] gh-135956: Remove duplicate word in _pydatetime docstring (GH-…

    21f9873

    [3.14] gh-135956: Remove duplicate word in _pydatetime docstring (GH-…

    3b5d82a
  10. terryjreedy commented on Jun 26, 2025

    @terryjreedy
    terryjreedy
    on Jun 26, 2025
    Member
    More actions

    @jason-mcgowan Thanks for catching this. @brianschubert Thanks for checking for more. Others have done this before, so I am surprised that this one got missed. Maybe just an oversight in the last round.

  11. terryjreedy
    closed this as completedon Jun 26, 2025
  12. StanFromIreland
    added this to Date and time issues 🕰️on Jun 26, 2025
  13. StanFromIreland
    moved this to Done in Date and time issues 🕰️on Jun 26, 2025
  14. StanFromIreland commented on Jun 26, 2025

    @StanFromIreland
    StanFromIreland
    on Jun 26, 2025
    Member
    More actions

    Other occurrences, limited to triple quoted docstrings, omitting tests, as I was getting too much noise otherwise:

    Private:

    ./Lib/asyncio/base_events.py:"""Prepare the run loop to process events.
    
            This method exists so that custom custom event loop subclasses (e.g., event loops
            that integrate a GUI event loop with Python's event loop) have access to all the
            loop setup logic.
            """.
    ./Lib/asyncio/base_events.py:"""Clean up after an event loop finishes the looping over events.
    
            This method exists so that custom custom event loop subclasses (e.g., event loops
            that integrate a GUI event loop with Python's event loop) have access to all the
            loop cleanup logic.
            """
    ./Lib/idlelib/editor.py:"""Return 2 lines containing block opener and and indent.
    
            Either the indent line or both may be None.
            """

    Public:

    ./Lib/unittest/mock.py:"""assert that the mock was called exactly once and that that call was
            with the specified arguments."""
    Reacted by Weilin Du
  15. LamentXU123 commented on Jun 26, 2025

    @LamentXU123
    LamentXU123
    on Jun 26, 2025
    Contributor
    More actions

    Other occurrences, limited to triple quoted docstrings, omitting tests, as I was getting too much noise otherwise:

    Private:

    ./Lib/asyncio/base_events.py:"""Prepare the run loop to process events.
    
            This method exists so that custom custom event loop subclasses (e.g., event loops
            that integrate a GUI event loop with Python's event loop) have access to all the
            loop setup logic.
            """.
    ./Lib/asyncio/base_events.py:"""Clean up after an event loop finishes the looping over events.
    
            This method exists so that custom custom event loop subclasses (e.g., event loops
            that integrate a GUI event loop with Python's event loop) have access to all the
            loop cleanup logic.
            """
    ./Lib/idlelib/editor.py:"""Return 2 lines containing block opener and and indent.
    
            Either the indent line or both may be None.
            """

    Public:

    ./Lib/unittest/mock.py:"""assert that the mock was called exactly once and that that call was
            with the specified arguments."""

    Great! May I include this in #135964?

  16. LamentXU123 commented on Jun 28, 2025

    @LamentXU123
    LamentXU123
    on Jun 28, 2025
    Contributor
    More actions

    Hi, @StanFromIreland friendly pinging here. These typos you've mentioned are still in the main branch, would you like me to open a PR to fix it?

  17. StanFromIreland commented on Jun 28, 2025

    @StanFromIreland
    StanFromIreland
    on Jun 28, 2025
    Member
    More actions

    You can fix the public one if you wish, though it's not high priority, I'm 0 on the others.

  18. LamentXU123 commented on Jun 28, 2025

    @LamentXU123
    LamentXU123
    on Jun 28, 2025
    Contributor
    More actions

    You can fix the public one if you wish, though it's not high priority, I'm 0 on the others.

    Sure! #136067

  19. AndPuQing
    added a commit that references this issue on Jul 11, 2025

    pythongh-135956: Remove duplicate word in _pydatetime docstring (pyth…

    cb689a3
  20. Pranjal095
    added a commit that references this issue on Jul 12, 2025

    pythongh-135956: Remove duplicate word in _pydatetime docstring (pyth…

    4fa4588
  21. taegyunkim
    added a commit that references this issue on Aug 4, 2025

    pythongh-135956: Remove duplicate word in _pydatetime docstring (pyth…

    266586b
  22. Agent-Hellboy
    added a commit that references this issue on Aug 19, 2025

    pythongh-135956: Remove duplicate word in _pydatetime docstring (pyth…

    d675178
  23. aisipos
    added a commit that references this issue on May 3, 2026

    pythongh-135956: Help prevent leaks in test_extra_response_headers_arg

    a249eea
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

    docsDocumentation in the Doc dirDocumentation in the Doc dir

    Projects

    • Date and time issues 🕰️
      Status
      Done
      Show more project fields
    • docs issues
      Status
      Todo
      Show more project fields

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.