From 50c797a3e03bed56662860bc96a9d900dd66b8b0 Mon Sep 17 00:00:00 2001 From: William Andrea Date: Mon, 24 Apr 2023 14:54:16 -0400 Subject: [PATCH] gh-99032: datetime docs: Encoding is no longer relevant (GH-93365) This removes a section of the `strftime` and `strptime` documentation that refers to a bygone era when `strftime` would return an encoded byte string. --------- (cherry picked from commit 2aa22f72fbbabb4ca2a641c0546d25c45128c56f) Co-authored-by: William Andrea Co-authored-by: Paul Ganssle <1377457+pganssle@users.noreply.github.com> --- Doc/library/datetime.rst | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst index d46eaade142e47..cea54d0935ac83 100644 --- a/Doc/library/datetime.rst +++ b/Doc/library/datetime.rst @@ -2502,10 +2502,7 @@ Notes: Because the format depends on the current locale, care should be taken when making assumptions about the output value. Field orderings will vary (for example, "month/day/year" versus "day/month/year"), and the output may - contain Unicode characters encoded using the locale's default encoding (for - example, if the current locale is ``ja_JP``, the default encoding could be - any one of ``eucJP``, ``SJIS``, or ``utf-8``; use :meth:`locale.getlocale` - to determine the current locale's encoding). + contain non-ASCII characters. (2) The :meth:`strptime` method can parse years in the full [1, 9999] range, but