gh-99032: datetime docs: Encoding is no longer relevant (#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.

---------

Co-authored-by: Paul Ganssle <1377457+pganssle@users.noreply.github.com>
This commit is contained in:
William Andrea 2023-04-24 14:54:16 -04:00 committed by GitHub
parent 5b404d6cad
commit 2aa22f72fb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -2510,10 +2510,7 @@ Notes:
Because the format depends on the current locale, care should be taken when Because the format depends on the current locale, care should be taken when
making assumptions about the output value. Field orderings will vary (for making assumptions about the output value. Field orderings will vary (for
example, "month/day/year" versus "day/month/year"), and the output may example, "month/day/year" versus "day/month/year"), and the output may
contain Unicode characters encoded using the locale's default encoding (for contain non-ASCII characters.
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).
(2) (2)
The :meth:`strptime` method can parse years in the full [1, 9999] range, but The :meth:`strptime` method can parse years in the full [1, 9999] range, but