Mar 9, 2025 · Mar 9, 2025 · Mar 9, 2025 · Mar 9, 2025 · Mar 9, 2025 · Mar 9, 2025
diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst
 Technical Detail
 ^^^^^^^^^^^^^^^^

 A :exc:`ValueError` will be raised if digits are not ASCII.

 Broadly speaking, ``d.strftime(fmt)`` acts like the :mod:`time` module's
 ``time.strftime(fmt, d.timetuple())`` although not all objects support a
 :meth:`~date.timetuple` method.
   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 non-ASCII characters.
   contain non-ASCII characters. :meth:`~.datetime.strptime` rejects non-ASCII
   digits for non-locale-specific numeric format codes (e.g. `%Y`, `%H`, etc).

 (2)
   The :meth:`~.datetime.strptime` method can parse years in the full [1, 9999] range, but
diff --git a/Doc/library/time.rst b/Doc/library/time.rst
   :func:`gmtime` or :func:`localtime` to a string as specified by the *format*
   argument.  If *t* is not provided, the current time as returned by
   :func:`localtime` is used.  *format* must be a string.  :exc:`ValueError` is
   raised if any field in *t* is outside of the allowed range or if digits are
   not ASCII.
   raised if any field in *t* is outside of the allowed range.

   0 is a legal argument for any position in the time tuple; if it is normally
   illegal the value is forced to a correct one.
      When used with the :func:`strptime` function, ``%U`` and ``%W`` are only used in
      calculations when the day of the week and the year are specified.

   (5)
      The :func:`strptime` function does not accept non-ASCII digits for numeric values.

   Here is an example, a format for dates compatible with that specified  in the
   :rfc:`2822` Internet email standard.  [1]_ ::
Original file line number	Diff line number	Diff line change
Expand Up		@@ -2617,8 +2617,6 @@ differences between platforms in handling of unsupported format specifiers.
		Technical Detail
		^^^^^^^^^^^^^^^^

		A :exc:`ValueError` will be raised if digits are not ASCII.

		Broadly speaking, ``d.strftime(fmt)`` acts like the :mod:`time` module's
		``time.strftime(fmt, d.timetuple())`` although not all objects support a
		:meth:`~date.timetuple` method.
Expand DownExpand Up		@@ -2655,7 +2653,8 @@ 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 non-ASCII characters.
		contain non-ASCII characters. :meth:`~.datetime.strptime` rejects non-ASCII
		digits for non-locale-specific numeric format codes (e.g. `%Y`, `%H`, etc).

		(2)
		The :meth:`~.datetime.strptime` method can parse years in the full [1, 9999] range, but
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -431,8 +431,7 @@ Functions
		:func:`gmtime` or :func:`localtime` to a string as specified by the format
		argument. If t is not provided, the current time as returned by
		:func:`localtime` is used. format must be a string. :exc:`ValueError` is
		raised if any field in t is outside of the allowed range or if digits are
		not ASCII.
		raised if any field in t is outside of the allowed range.

		0 is a legal argument for any position in the time tuple; if it is normally
		illegal the value is forced to a correct one.
Expand DownExpand Up		@@ -564,6 +563,9 @@ Functions
		When used with the :func:`strptime` function, ``%U`` and ``%W`` are only used in
		calculations when the day of the week and the year are specified.

		(5)
		The :func:`strptime` function does not accept non-ASCII digits for numeric values.
Copy link Member picnixzApr 1, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Should we mention the "non-locale-specific numeric format codes" here or, since it's not officially supported, we can be a bit lazy? Copy link ContributorAuthor StanFromIrelandApr 1, 2025 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. @pganssle Do you want to do this too? Or should I?

		Here is an example, a format for dates compatible with that specified in the
		:rfc:`2822` Internet email standard. [1]_ ::

Expand Down