]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
gh-70647: Better promote how to safely parse yearless dates in datetime. (GH-116179)
authorGregory P. Smith <68491+gpshead@users.noreply.github.com>
Sun, 21 Dec 2025 06:47:40 +0000 (22:47 -0800)
committerGitHub <noreply@github.com>
Sun, 21 Dec 2025 06:47:40 +0000 (22:47 -0800)
commitb8d3fddba6e96e693ced0d3b8f6ddbd61428fd32
tree810c4f408b766d2c1fb046d9e6893987f7c43f5f
parent8d2d7bb2e754f8649a68ce4116271a4932f76907
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
Doc/library/datetime.rst