mirror of
https://github.com/python/cpython
synced 2024-10-14 10:48:24 +00:00
#14766: Reflow the altered paragraphs.
This commit is contained in:
parent
9075d8b771
commit
539f239e88
|
@ -12,8 +12,8 @@
|
|||
The :mod:`datetime` module supplies classes for manipulating dates and times in
|
||||
both simple and complex ways. While date and time arithmetic is supported, the
|
||||
focus of the implementation is on efficient attribute extraction for output
|
||||
formatting and manipulation. For related
|
||||
functionality, see also the :mod:`time` and :mod:`calendar` modules.
|
||||
formatting and manipulation. For related functionality, see also the
|
||||
:mod:`time` and :mod:`calendar` modules.
|
||||
|
||||
There are two kinds of date and time objects: "naive" and "aware".
|
||||
|
||||
|
@ -25,22 +25,21 @@ interpretation [#]_.
|
|||
|
||||
A naive object does not contain enough information to unambiguously locate
|
||||
itself relative to other date/time objects. Whether a naive object represents
|
||||
Coordinated Universal Time (UTC),
|
||||
local time, or time in some other timezone is purely up to the program, just
|
||||
like it's up to the program whether a particular number represents metres,
|
||||
miles, or mass. Naive objects are easy to understand and to
|
||||
work with, at the cost of ignoring some aspects of reality.
|
||||
Coordinated Universal Time (UTC), local time, or time in some other timezone is
|
||||
purely up to the program, just like it is up to the program whether a
|
||||
particular number represents metres, miles, or mass. Naive objects are easy to
|
||||
understand and to work with, at the cost of ignoring some aspects of reality.
|
||||
|
||||
For applications requiring aware objects, :class:`.datetime` and :class:`.time` objects
|
||||
have an optional time zone information attribute, :attr:`tzinfo`, that can be
|
||||
set to an instance of a subclass of the abstract :class:`tzinfo` class. These
|
||||
:class:`tzinfo` objects capture information about the offset from UTC time, the
|
||||
time zone name, and whether Daylight Saving Time is in effect. Note that only
|
||||
one concrete :class:`tzinfo` class, the :class:`timezone` class, is supplied by the
|
||||
:mod:`datetime` module. The :class:`timezone` class can represent simple
|
||||
timezones with fixed offset from UTC such as UTC itself or North American EST and
|
||||
EDT timezones. Supporting timezones at deeper levels of detail is
|
||||
up to the application. The rules for time adjustment across the
|
||||
For applications requiring aware objects, :class:`.datetime` and :class:`.time`
|
||||
objects have an optional time zone information attribute, :attr:`tzinfo`, that
|
||||
can be set to an instance of a subclass of the abstract :class:`tzinfo` class.
|
||||
These :class:`tzinfo` objects capture information about the offset from UTC
|
||||
time, the time zone name, and whether Daylight Saving Time is in effect. Note
|
||||
that only one concrete :class:`tzinfo` class, the :class:`timezone` class, is
|
||||
supplied by the :mod:`datetime` module. The :class:`timezone` class can
|
||||
represent simple timezones with fixed offset from UTC, such as UTC itself or
|
||||
North American EST and EDT timezones. Supporting timezones at deeper levels of
|
||||
detail is up to the application. The rules for time adjustment across the
|
||||
world are more political than rational, change frequently, and there is no
|
||||
standard suitable for every application aside from UTC.
|
||||
|
||||
|
|
Loading…
Reference in a new issue