]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.13] gh-70647: Better promote how to safely parse yearless dates in datetime. ...
authorGregory P. Smith <68491+gpshead@users.noreply.github.com>
Sun, 21 Dec 2025 07:03:24 +0000 (23:03 -0800)
committerGitHub <noreply@github.com>
Sun, 21 Dec 2025 07:03:24 +0000 (07:03 +0000)
commit9b7a6286327b0e03d258316dde7419ca0a7e10f3
tree9a3644a962c04f254bedaff17606b1f11f6087ab
parenta696ba8b4d42fd632afc9bc88ad830a2e4cceed8
[3.13] gh-70647: Better promote how to safely parse yearless dates in datetime. (GH-116179) (#143038)

* gh-70647: Better promote how to safely parse yearless dates in datetime. (GH-116179)

* gh-70647: Better promote how to safely parse yearless dates in datetime.

Every four years people encounter this because it just isn't obvious.
This moves the footnote up to a note with a code example.

We'd love to change the default year value for datetime but doing
that could have other consequences for existing code.  This documented
workaround *always* works.

* doctest code within note is bad, dedent.

* Update to match the error message.

* remove no longer referenced footnote

* ignore the warning in the doctest

* use Petr's suggestion for the docs to hide the warning processing

* cover date.strptime (3.14) as well

* remove date.strptime mentions from 3.14
Doc/library/datetime.rst