From 678c5c07521caca809b1356d954975e6234c49ae Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sat, 12 Jan 2019 09:27:30 -0800 Subject: [PATCH] bpo-34512: Document platform-specific strftime() behavior for non-ASCII format strings (GH-8948) (cherry picked from commit 1cffd0eed313011c0c2bb071c8affeb4a7ed05c7) Co-authored-by: Alexey Izbyshev --- Doc/library/datetime.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst index db3a6522c24..121f73bbe85 100644 --- a/Doc/library/datetime.rst +++ b/Doc/library/datetime.rst @@ -2034,6 +2034,12 @@ calls the platform C library's :func:`strftime` function, and platform variations are common. To see the full set of format codes supported on your platform, consult the :manpage:`strftime(3)` documentation. +For the same reason, handling of format strings containing Unicode code points +that can't be represented in the charset of the current locale is also +platform-dependent. On some platforms such code points are preserved intact in +the output, while on others ``strftime`` may raise :exc:`UnicodeError` or return +an empty string instead. + The following is a list of all the format codes that the C standard (1989 version) requires, and these work on all platforms with a standard C implementation. Note that the 1999 version of the C standard added additional