### 导航
- [索引](../genindex.xhtml "总目录")
- [模块](../py-modindex.xhtml "Python 模块索引") |
- [下一页](calendar.xhtml "calendar --- General calendar-related functions") |
- [上一页](datatypes.xhtml "数据类型") |
- ![](https://box.kancloud.cn/a721fc7ec672275e257bbbfde49a4d4e_16x16.png)
- [Python](https://www.python.org/) »
- zh\_CN 3.7.3 [文档](../index.xhtml) »
- [Python 标准库](index.xhtml) »
- [数据类型](datatypes.xhtml) »
- $('.inline-search').show(0); |
# [`datetime`](#module-datetime "datetime: Basic date and time types.") --- 基础日期/时间数据类型
**源代码:** [Lib/datetime.py](https://github.com/python/cpython/tree/3.7/Lib/datetime.py) \[https://github.com/python/cpython/tree/3.7/Lib/datetime.py\]
- - - - - -
[`datetime`](#module-datetime "datetime: Basic date and time types.") 模块提供了用于以简单和复杂的方式操作日期和时间的类。在支持日期时间数学运算的同时,实现的关注点更着重于如何能够更有效地解析其属性用于格式化输出和数据操作。相关功能还可以参阅 [`time`](time.xhtml#module-time "time: Time access and conversions.") 和 [`calendar`](calendar.xhtml#module-calendar "calendar: Functions for working with calendars, including some emulation of the Unix cal program.") 模块。
有两种日期和时间的对象:“naive”和“aware”。
一个“aware”对象有着用足以支持一些应用层面算法和国家层面时间调整的信息,例如时区和夏令时,来让自己和其他的“aware”对象区别开来。一个“aware”对象是用来表达不对解释器开放的时间点信息的 [1](#id2)。
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 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, [`datetime`](#datetime.datetime "datetime.datetime") and [`time`](#datetime.time "datetime.time")objects have an optional time zone information attribute, `tzinfo`, that can be set to an instance of a subclass of the abstract [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") class. These [`tzinfo`](#datetime.tzinfo "datetime.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 [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") class, the [`timezone`](#datetime.timezone "datetime.timezone") class, is supplied by the [`datetime`](#module-datetime "datetime: Basic date and time types.") module. The [`timezone`](#datetime.timezone "datetime.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.
The [`datetime`](#module-datetime "datetime: Basic date and time types.") module exports the following constants:
`datetime.``MINYEAR`The smallest year number allowed in a [`date`](#datetime.date "datetime.date") or [`datetime`](#datetime.datetime "datetime.datetime") object. [`MINYEAR`](#datetime.MINYEAR "datetime.MINYEAR") is `1`.
`datetime.``MAXYEAR`The largest year number allowed in a [`date`](#datetime.date "datetime.date") or [`datetime`](#datetime.datetime "datetime.datetime") object. [`MAXYEAR`](#datetime.MAXYEAR "datetime.MAXYEAR") is `9999`.
参见
模块 [`calendar`](calendar.xhtml#module-calendar "calendar: Functions for working with calendars, including some emulation of the Unix cal program.")日历相关一般函数
模块 [`time`](time.xhtml#module-time "time: Time access and conversions.")时间的访问和转换
## Available Types
*class* `datetime.``date`An idealized naive date, assuming the current Gregorian calendar always was, and always will be, in effect. Attributes: [`year`](#datetime.date.year "datetime.date.year"), [`month`](#datetime.date.month "datetime.date.month"), and [`day`](#datetime.date.day "datetime.date.day").
*class* `datetime.``time`An idealized time, independent of any particular day, assuming that every day has exactly 24\*60\*60 seconds (there is no notion of "leap seconds" here). Attributes: [`hour`](#datetime.time.hour "datetime.time.hour"), [`minute`](#datetime.time.minute "datetime.time.minute"), [`second`](#datetime.time.second "datetime.time.second"), [`microsecond`](#datetime.time.microsecond "datetime.time.microsecond"), and [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo").
*class* `datetime.``datetime`A combination of a date and a time. Attributes: [`year`](#datetime.datetime.year "datetime.datetime.year"), [`month`](#datetime.datetime.month "datetime.datetime.month"), [`day`](#datetime.datetime.day "datetime.datetime.day"), [`hour`](#datetime.datetime.hour "datetime.datetime.hour"), [`minute`](#datetime.datetime.minute "datetime.datetime.minute"), [`second`](#datetime.datetime.second "datetime.datetime.second"), [`microsecond`](#datetime.datetime.microsecond "datetime.datetime.microsecond"), and [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo").
*class* `datetime.``timedelta`A duration expressing the difference between two [`date`](#datetime.date "datetime.date"), [`time`](#datetime.time "datetime.time"), or [`datetime`](#datetime.datetime "datetime.datetime") instances to microsecond resolution.
*class* `datetime.``tzinfo`An abstract base class for time zone information objects. These are used by the [`datetime`](#datetime.datetime "datetime.datetime") and [`time`](#datetime.time "datetime.time") classes to provide a customizable notion of time adjustment (for example, to account for time zone and/or daylight saving time).
*class* `datetime.``timezone`A class that implements the [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") abstract base class as a fixed offset from the UTC.
3\.2 新版功能.
Objects of these types are immutable.
Objects of the [`date`](#datetime.date "datetime.date") type are always naive.
An object of type [`time`](#datetime.time "datetime.time") or [`datetime`](#datetime.datetime "datetime.datetime") may be naive or aware. A [`datetime`](#datetime.datetime "datetime.datetime") object *d* is aware if `d.tzinfo` is not `None` and `d.tzinfo.utcoffset(d)` does not return `None`. If `d.tzinfo` is `None`, or if `d.tzinfo` is not `None` but `d.tzinfo.utcoffset(d)`returns `None`, *d* is naive. A [`time`](#datetime.time "datetime.time") object *t* is aware if `t.tzinfo` is not `None` and `t.tzinfo.utcoffset(None)` does not return `None`. Otherwise, *t* is naive.
The distinction between naive and aware doesn't apply to [`timedelta`](#datetime.timedelta "datetime.timedelta")objects.
Subclass relationships:
```
object
timedelta
tzinfo
timezone
time
date
datetime
```
## [`timedelta`](#datetime.timedelta "datetime.timedelta") Objects
A [`timedelta`](#datetime.timedelta "datetime.timedelta") object represents a duration, the difference between two dates or times.
*class* `datetime.``timedelta`(*days=0*, *seconds=0*, *microseconds=0*, *milliseconds=0*, *minutes=0*, *hours=0*, *weeks=0*)All arguments are optional and default to `0`. Arguments may be integers or floats, and may be positive or negative.
Only *days*, *seconds* and *microseconds* are stored internally. Arguments are converted to those units:
- A millisecond is converted to 1000 microseconds.
- A minute is converted to 60 seconds.
- An hour is converted to 3600 seconds.
- A week is converted to 7 days.
and days, seconds and microseconds are then normalized so that the representation is unique, with
- `0 <= microseconds < 1000000`
- `0 <= seconds < 3600*24` (the number of seconds in one day)
- `-999999999 <= days <= 999999999`
If any argument is a float and there are fractional microseconds, the fractional microseconds left over from all arguments are combined and their sum is rounded to the nearest microsecond using round-half-to-even tiebreaker. If no argument is a float, the conversion and normalization processes are exact (no information is lost).
If the normalized value of days lies outside the indicated range, [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") is raised.
Note that normalization of negative values may be surprising at first. For example,
```
>>> from datetime import timedelta
>>> d = timedelta(microseconds=-1)
>>> (d.days, d.seconds, d.microseconds)
(-1, 86399, 999999)
```
Class attributes are:
`timedelta.``min`The most negative [`timedelta`](#datetime.timedelta "datetime.timedelta") object, `timedelta(-999999999)`.
`timedelta.``max`The most positive [`timedelta`](#datetime.timedelta "datetime.timedelta") object,
```
timedelta(days=999999999,
hours=23, minutes=59, seconds=59, microseconds=999999)
```
.
`timedelta.``resolution`The smallest possible difference between non-equal [`timedelta`](#datetime.timedelta "datetime.timedelta") objects, `timedelta(microseconds=1)`.
Note that, because of normalization, `timedelta.max` > `-timedelta.min`. `-timedelta.max` is not representable as a [`timedelta`](#datetime.timedelta "datetime.timedelta") object.
实例属性(只读):
属性
值
`days`
-999999999 至 999999999(含)
`seconds`
0 至 86399(含)
`microseconds`
0 至 999999(含)
支持的操作:
运算
结果
`t1 = t2 + t3`
Sum of *t2* and *t3*. Afterwards *t1*-*t2* == *t3* and *t1*-*t3* == *t2* are true. (1)
`t1 = t2 - t3`
Difference of *t2* and *t3*. Afterwards *t1*== *t2* - *t3* and *t2* == *t1* + *t3* are true. (1)(6)
`t1 = t2 * i or t1 = i * t2`
Delta multiplied by an integer. Afterwards *t1* // i == *t2* is true, provided `i != 0`.
In general, *t1* \* i == *t1* \* (i-1) + *t1*is true. (1)
`t1 = t2 * f or t1 = f * t2`
Delta multiplied by a float. The result is rounded to the nearest multiple of timedelta.resolution using round-half-to-even.
`f = t2 / t3`
Division (3) of overall duration *t2* by interval unit *t3*. Returns a [`float`](functions.xhtml#float "float")object.
`t1 = t2 / f or t1 = t2 / i`
Delta divided by a float or an int. The result is rounded to the nearest multiple of timedelta.resolution using round-half-to-even.
`t1 = t2 // i` or `t1 = t2 // t3`
The floor is computed and the remainder (if any) is thrown away. In the second case, an integer is returned. (3)
`t1 = t2 % t3`
The remainder is computed as a [`timedelta`](#datetime.timedelta "datetime.timedelta") object. (3)
`q, r = divmod(t1, t2)`
Computes the quotient and the remainder: `q = t1 // t2` (3) and `r = t1 % t2`. q is an integer and r is a [`timedelta`](#datetime.timedelta "datetime.timedelta")object.
`+t1`
Returns a [`timedelta`](#datetime.timedelta "datetime.timedelta") object with the same value. (2)
`-t1`
equivalent to [`timedelta`](#datetime.timedelta "datetime.timedelta")(-*t1.days*, -*t1.seconds*, -*t1.microseconds*), and to *t1*\* -1. (1)(4)
`abs(t)`
equivalent to +*t* when `t.days >= 0`, and to -*t* when `t.days < 0`. (2)
`str(t)`
Returns a string in the form `[D day[s], ][H]H:MM:SS[.UUUUUU]`, where D is negative for negative `t`. (5)
`repr(t)`
Returns a string representation of the [`timedelta`](#datetime.timedelta "datetime.timedelta") object as a constructor call with canonical attribute values.
注释:
1. This is exact, but may overflow.
2. This is exact, and cannot overflow.
3. Division by 0 raises [`ZeroDivisionError`](exceptions.xhtml#ZeroDivisionError "ZeroDivisionError").
4. -*timedelta.max* is not representable as a [`timedelta`](#datetime.timedelta "datetime.timedelta") object.
5. String representations of [`timedelta`](#datetime.timedelta "datetime.timedelta") objects are normalized similarly to their internal representation. This leads to somewhat unusual results for negative timedeltas. For example:
```
>>> timedelta(hours=-5)
datetime.timedelta(days=-1, seconds=68400)
>>> print(_)
-1 day, 19:00:00
```
6. The expression `t2 - t3` will always be equal to the expression `t2 + (-t3)` except when t3 is equal to `timedelta.max`; in that case the former will produce a result while the latter will overflow.
In addition to the operations listed above [`timedelta`](#datetime.timedelta "datetime.timedelta") objects support certain additions and subtractions with [`date`](#datetime.date "datetime.date") and [`datetime`](#datetime.datetime "datetime.datetime")objects (see below).
在 3.2 版更改: Floor division and true division of a [`timedelta`](#datetime.timedelta "datetime.timedelta") object by another [`timedelta`](#datetime.timedelta "datetime.timedelta") object are now supported, as are remainder operations and the [`divmod()`](functions.xhtml#divmod "divmod") function. True division and multiplication of a [`timedelta`](#datetime.timedelta "datetime.timedelta") object by a [`float`](functions.xhtml#float "float") object are now supported.
Comparisons of [`timedelta`](#datetime.timedelta "datetime.timedelta") objects are supported with the [`timedelta`](#datetime.timedelta "datetime.timedelta") object representing the smaller duration considered to be the smaller timedelta. In order to stop mixed-type comparisons from falling back to the default comparison by object address, when a [`timedelta`](#datetime.timedelta "datetime.timedelta") object is compared to an object of a different type, [`TypeError`](exceptions.xhtml#TypeError "TypeError") is raised unless the comparison is `==` or `!=`. The latter cases return [`False`](constants.xhtml#False "False") or [`True`](constants.xhtml#True "True"), respectively.
[`timedelta`](#datetime.timedelta "datetime.timedelta") objects are [hashable](../glossary.xhtml#term-hashable) (usable as dictionary keys), support efficient pickling, and in Boolean contexts, a [`timedelta`](#datetime.timedelta "datetime.timedelta") object is considered to be true if and only if it isn't equal to `timedelta(0)`.
Instance methods:
`timedelta.``total_seconds`()Return the total number of seconds contained in the duration. Equivalent to `td / timedelta(seconds=1)`. For interval units other than seconds, use the division form directly (e.g. `td / timedelta(microseconds=1)`).
Note that for very large time intervals (greater than 270 years on most platforms) this method will lose microsecond accuracy.
3\.2 新版功能.
Example usage:
```
>>> from datetime import timedelta
>>> year = timedelta(days=365)
>>> another_year = timedelta(weeks=40, days=84, hours=23,
... minutes=50, seconds=600) # adds up to 365 days
>>> year.total_seconds()
31536000.0
>>> year == another_year
True
>>> ten_years = 10 * year
>>> ten_years, ten_years.days // 365
(datetime.timedelta(days=3650), 10)
>>> nine_years = ten_years - year
>>> nine_years, nine_years.days // 365
(datetime.timedelta(days=3285), 9)
>>> three_years = nine_years // 3
>>> three_years, three_years.days // 365
(datetime.timedelta(days=1095), 3)
>>> abs(three_years - ten_years) == 2 * three_years + year
True
```
## [`date`](#datetime.date "datetime.date") Objects
A [`date`](#datetime.date "datetime.date") object represents a date (year, month and day) in an idealized calendar, the current Gregorian calendar indefinitely extended in both directions. January 1 of year 1 is called day number 1, January 2 of year 1 is called day number 2, and so on. This matches the definition of the "proleptic Gregorian" calendar in Dershowitz and Reingold's book Calendrical Calculations, where it's the base calendar for all computations. See the book for algorithms for converting between proleptic Gregorian ordinals and many other calendar systems.
*class* `datetime.``date`(*year*, *month*, *day*)All arguments are required. Arguments may be integers, in the following ranges:
- `MINYEAR <= year <= MAXYEAR`
- `1 <= month <= 12`
- `1 <= day <= number of days in the given month and year`
If an argument outside those ranges is given, [`ValueError`](exceptions.xhtml#ValueError "ValueError") is raised.
Other constructors, all class methods:
*classmethod* `date.``today`()Return the current local date. This is equivalent to `date.fromtimestamp(time.time())`.
*classmethod* `date.``fromtimestamp`(*timestamp*)Return the local date corresponding to the POSIX timestamp, such as is returned by [`time.time()`](time.xhtml#time.time "time.time"). This may raise [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError"), if the timestamp is out of the range of values supported by the platform C `localtime()` function, and [`OSError`](exceptions.xhtml#OSError "OSError") on `localtime()` failure. It's common for this to be restricted to years from 1970 through 2038. Note that on non-POSIX systems that include leap seconds in their notion of a timestamp, leap seconds are ignored by [`fromtimestamp()`](#datetime.date.fromtimestamp "datetime.date.fromtimestamp").
在 3.3 版更改: Raise [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") instead of [`ValueError`](exceptions.xhtml#ValueError "ValueError") if the timestamp is out of the range of values supported by the platform C `localtime()` function. Raise [`OSError`](exceptions.xhtml#OSError "OSError") instead of [`ValueError`](exceptions.xhtml#ValueError "ValueError") on `localtime()` failure.
*classmethod* `date.``fromordinal`(*ordinal*)Return the date corresponding to the proleptic Gregorian ordinal, where January 1 of year 1 has ordinal 1. [`ValueError`](exceptions.xhtml#ValueError "ValueError") is raised unless
```
1 <= ordinal <=
date.max.toordinal()
```
. For any date *d*,
```
date.fromordinal(d.toordinal()) ==
d
```
.
*classmethod* `date.``fromisoformat`(*date\_string*)Return a [`date`](#datetime.date "datetime.date") corresponding to a *date\_string* in the format emitted by [`date.isoformat()`](#datetime.date.isoformat "datetime.date.isoformat"). Specifically, this function supports strings in the format(s) `YYYY-MM-DD`.
警告
This does not support parsing arbitrary ISO 8601 strings - it is only intended as the inverse operation of [`date.isoformat()`](#datetime.date.isoformat "datetime.date.isoformat").
3\.7 新版功能.
Class attributes:
`date.``min`The earliest representable date, `date(MINYEAR, 1, 1)`.
`date.``max`The latest representable date, `date(MAXYEAR, 12, 31)`.
`date.``resolution`The smallest possible difference between non-equal date objects, `timedelta(days=1)`.
实例属性(只读):
`date.``year`Between [`MINYEAR`](#datetime.MINYEAR "datetime.MINYEAR") and [`MAXYEAR`](#datetime.MAXYEAR "datetime.MAXYEAR") inclusive.
`date.``month`1 至 12(含)
`date.``day`Between 1 and the number of days in the given month of the given year.
支持的操作:
运算
结果
`date2 = date1 + timedelta`
*date2* is `timedelta.days` days removed from *date1*. (1)
`date2 = date1 - timedelta`
Computes *date2* such that
```
date2 +
timedelta == date1
```
. (2)
`timedelta = date1 - date2`
(3)
`date1 < date2`
*date1* is considered less than *date2* when *date1* precedes *date2* in time. (4)
注释:
1. *date2* is moved forward in time if `timedelta.days > 0`, or backward if `timedelta.days < 0`. Afterward `date2 - date1 == timedelta.days`. `timedelta.seconds` and `timedelta.microseconds` are ignored. [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") is raised if `date2.year` would be smaller than [`MINYEAR`](#datetime.MINYEAR "datetime.MINYEAR") or larger than [`MAXYEAR`](#datetime.MAXYEAR "datetime.MAXYEAR").
2. `timedelta.seconds` and `timedelta.microseconds` are ignored.
3. This is exact, and cannot overflow. timedelta.seconds and timedelta.microseconds are 0, and date2 + timedelta == date1 after.
4. In other words, `date1 < date2` if and only if
```
date1.toordinal() <
date2.toordinal()
```
. Date comparison raises [`TypeError`](exceptions.xhtml#TypeError "TypeError") if the other comparand isn't also a [`date`](#datetime.date "datetime.date") object. However, `NotImplemented` is returned instead if the other comparand has a `timetuple()` attribute. This hook gives other kinds of date objects a chance at implementing mixed-type comparison. If not, when a [`date`](#datetime.date "datetime.date")object is compared to an object of a different type, [`TypeError`](exceptions.xhtml#TypeError "TypeError") is raised unless the comparison is `==` or `!=`. The latter cases return [`False`](constants.xhtml#False "False") or [`True`](constants.xhtml#True "True"), respectively.
Dates can be used as dictionary keys. In Boolean contexts, all [`date`](#datetime.date "datetime.date")objects are considered to be true.
Instance methods:
`date.``replace`(*year=self.year*, *month=self.month*, *day=self.day*)Return a date with the same value, except for those parameters given new values by whichever keyword arguments are specified. For example, if
```
d ==
date(2002, 12, 31)
```
, then `d.replace(day=26) == date(2002, 12, 26)`.
`date.``timetuple`()Return a [`time.struct_time`](time.xhtml#time.struct_time "time.struct_time") such as returned by [`time.localtime()`](time.xhtml#time.localtime "time.localtime"). The hours, minutes and seconds are 0, and the DST flag is -1. `d.timetuple()`is equivalent to
```
time.struct_time((d.year, d.month, d.day, 0, 0, 0,
d.weekday(), yday, -1))
```
, where
```
yday = d.toordinal() - date(d.year, 1,
1\).toordinal() + 1
```
is the day number within the current year starting with `1` for January 1st.
`date.``toordinal`()Return the proleptic Gregorian ordinal of the date, where January 1 of year 1 has ordinal 1. For any [`date`](#datetime.date "datetime.date") object *d*, `date.fromordinal(d.toordinal()) == d`.
`date.``weekday`()Return the day of the week as an integer, where Monday is 0 and Sunday is 6. For example, `date(2002, 12, 4).weekday() == 2`, a Wednesday. See also [`isoweekday()`](#datetime.date.isoweekday "datetime.date.isoweekday").
`date.``isoweekday`()Return the day of the week as an integer, where Monday is 1 and Sunday is 7. For example, `date(2002, 12, 4).isoweekday() == 3`, a Wednesday. See also [`weekday()`](#datetime.date.weekday "datetime.date.weekday"), [`isocalendar()`](#datetime.date.isocalendar "datetime.date.isocalendar").
`date.``isocalendar`()Return a 3-tuple, (ISO year, ISO week number, ISO weekday).
The ISO calendar is a widely used variant of the Gregorian calendar. See <https://www.staff.science.uu.nl/~gent0113/calendar/isocalendar.htm> for a good explanation.
The ISO year consists of 52 or 53 full weeks, and where a week starts on a Monday and ends on a Sunday. The first week of an ISO year is the first (Gregorian) calendar week of a year containing a Thursday. This is called week number 1, and the ISO year of that Thursday is the same as its Gregorian year.
For example, 2004 begins on a Thursday, so the first week of ISO year 2004 begins on Monday, 29 Dec 2003 and ends on Sunday, 4 Jan 2004, so that `date(2003, 12, 29).isocalendar() == (2004, 1, 1)` and
```
date(2004, 1,
4\).isocalendar() == (2004, 1, 7)
```
.
`date.``isoformat`()Return a string representing the date in ISO 8601 format, 'YYYY-MM-DD'. For example, `date(2002, 12, 4).isoformat() == '2002-12-04'`.
`date.``__str__`()For a date *d*, `str(d)` is equivalent to `d.isoformat()`.
`date.``ctime`()Return a string representing the date, for example
```
date(2002, 12,
4\).ctime() == 'Wed Dec 4 00:00:00 2002'
```
. `d.ctime()` is equivalent to `time.ctime(time.mktime(d.timetuple()))` on platforms where the native C `ctime()` function (which [`time.ctime()`](time.xhtml#time.ctime "time.ctime") invokes, but which [`date.ctime()`](#datetime.date.ctime "datetime.date.ctime") does not invoke) conforms to the C standard.
`date.``strftime`(*format*)Return a string representing the date, controlled by an explicit format string. Format codes referring to hours, minutes or seconds will see 0 values. For a complete list of formatting directives, see [strftime() and strptime() Behavior](#strftime-strptime-behavior).
`date.``__format__`(*format*)Same as [`date.strftime()`](#datetime.date.strftime "datetime.date.strftime"). This makes it possible to specify a format string for a [`date`](#datetime.date "datetime.date") object in [formatted string literals](../reference/lexical_analysis.xhtml#f-strings) and when using [`str.format()`](stdtypes.xhtml#str.format "str.format"). For a complete list of formatting directives, see [strftime() and strptime() Behavior](#strftime-strptime-behavior).
Example of counting days to an event:
```
>>> import time
>>> from datetime import date
>>> today = date.today()
>>> today
datetime.date(2007, 12, 5)
>>> today == date.fromtimestamp(time.time())
True
>>> my_birthday = date(today.year, 6, 24)
>>> if my_birthday < today:
... my_birthday = my_birthday.replace(year=today.year + 1)
>>> my_birthday
datetime.date(2008, 6, 24)
>>> time_to_birthday = abs(my_birthday - today)
>>> time_to_birthday.days
202
```
Example of working with [`date`](#datetime.date "datetime.date"):
```
>>> from datetime import date
>>> d = date.fromordinal(730920) # 730920th day after 1. 1. 0001
>>> d
datetime.date(2002, 3, 11)
>>> t = d.timetuple()
>>> for i in t:
... print(i)
2002 # year
3 # month
11 # day
0
0
0
0 # weekday (0 = Monday)
70 # 70th day in the year
-1
>>> ic = d.isocalendar()
>>> for i in ic:
... print(i)
2002 # ISO year
11 # ISO week number
1 # ISO day number ( 1 = Monday )
>>> d.isoformat()
'2002-03-11'
>>> d.strftime("%d/%m/%y")
'11/03/02'
>>> d.strftime("%A %d. %B %Y")
'Monday 11. March 2002'
>>> 'The {1} is {0:%d}, the {2} is {0:%B}.'.format(d, "day", "month")
'The day is 11, the month is March.'
```
## [`datetime`](#datetime.datetime "datetime.datetime") Objects
A [`datetime`](#datetime.datetime "datetime.datetime") object is a single object containing all the information from a [`date`](#datetime.date "datetime.date") object and a [`time`](#datetime.time "datetime.time") object. Like a [`date`](#datetime.date "datetime.date")object, [`datetime`](#datetime.datetime "datetime.datetime") assumes the current Gregorian calendar extended in both directions; like a time object, [`datetime`](#datetime.datetime "datetime.datetime") assumes there are exactly 3600\*24 seconds in every day.
Constructor:
*class* `datetime.``datetime`(*year*, *month*, *day*, *hour=0*, *minute=0*, *second=0*, *microsecond=0*, *tzinfo=None*, *\**, *fold=0*)The year, month and day arguments are required. *tzinfo* may be `None`, or an instance of a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass. The remaining arguments may be integers, in the following ranges:
- `MINYEAR <= year <= MAXYEAR`,
- `1 <= month <= 12`,
- `1 <= day <= number of days in the given month and year`,
- `0 <= hour < 24`,
- `0 <= minute < 60`,
- `0 <= second < 60`,
- `0 <= microsecond < 1000000`,
- `fold in [0, 1]`.
If an argument outside those ranges is given, [`ValueError`](exceptions.xhtml#ValueError "ValueError") is raised.
3\.6 新版功能: Added the `fold` argument.
Other constructors, all class methods:
*classmethod* `datetime.``today`()Return the current local datetime, with [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo")`None`. This is equivalent to `datetime.fromtimestamp(time.time())`. See also [`now()`](#datetime.datetime.now "datetime.datetime.now"), [`fromtimestamp()`](#datetime.datetime.fromtimestamp "datetime.datetime.fromtimestamp").
*classmethod* `datetime.``now`(*tz=None*)Return the current local date and time. If optional argument *tz* is `None`or not specified, this is like [`today()`](#datetime.datetime.today "datetime.datetime.today"), but, if possible, supplies more precision than can be gotten from going through a [`time.time()`](time.xhtml#time.time "time.time") timestamp (for example, this may be possible on platforms supplying the C `gettimeofday()` function).
If *tz* is not `None`, it must be an instance of a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass, and the current date and time are converted to *tz*’s time zone. In this case the result is equivalent to `tz.fromutc(datetime.utcnow().replace(tzinfo=tz))`. See also [`today()`](#datetime.datetime.today "datetime.datetime.today"), [`utcnow()`](#datetime.datetime.utcnow "datetime.datetime.utcnow").
*classmethod* `datetime.``utcnow`()Return the current UTC date and time, with [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo")`None`. This is like [`now()`](#datetime.datetime.now "datetime.datetime.now"), but returns the current UTC date and time, as a naive [`datetime`](#datetime.datetime "datetime.datetime") object. An aware current UTC datetime can be obtained by calling `datetime.now(timezone.utc)`. See also [`now()`](#datetime.datetime.now "datetime.datetime.now").
*classmethod* `datetime.``fromtimestamp`(*timestamp*, *tz=None*)Return the local date and time corresponding to the POSIX timestamp, such as is returned by [`time.time()`](time.xhtml#time.time "time.time"). If optional argument *tz* is `None` or not specified, the timestamp is converted to the platform's local date and time, and the returned [`datetime`](#datetime.datetime "datetime.datetime") object is naive.
If *tz* is not `None`, it must be an instance of a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass, and the timestamp is converted to *tz*’s time zone. In this case the result is equivalent to `tz.fromutc(datetime.utcfromtimestamp(timestamp).replace(tzinfo=tz))`.
[`fromtimestamp()`](#datetime.datetime.fromtimestamp "datetime.datetime.fromtimestamp") may raise [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError"), if the timestamp is out of the range of values supported by the platform C `localtime()` or `gmtime()` functions, and [`OSError`](exceptions.xhtml#OSError "OSError") on `localtime()` or `gmtime()` failure. It's common for this to be restricted to years in 1970 through 2038. Note that on non-POSIX systems that include leap seconds in their notion of a timestamp, leap seconds are ignored by [`fromtimestamp()`](#datetime.datetime.fromtimestamp "datetime.datetime.fromtimestamp"), and then it's possible to have two timestamps differing by a second that yield identical [`datetime`](#datetime.datetime "datetime.datetime") objects. See also [`utcfromtimestamp()`](#datetime.datetime.utcfromtimestamp "datetime.datetime.utcfromtimestamp").
在 3.3 版更改: Raise [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") instead of [`ValueError`](exceptions.xhtml#ValueError "ValueError") if the timestamp is out of the range of values supported by the platform C `localtime()` or `gmtime()` functions. Raise [`OSError`](exceptions.xhtml#OSError "OSError")instead of [`ValueError`](exceptions.xhtml#ValueError "ValueError") on `localtime()` or `gmtime()`failure.
在 3.6 版更改: [`fromtimestamp()`](#datetime.datetime.fromtimestamp "datetime.datetime.fromtimestamp") may return instances with [`fold`](#datetime.datetime.fold "datetime.datetime.fold") set to 1.
*classmethod* `datetime.``utcfromtimestamp`(*timestamp*)Return the UTC [`datetime`](#datetime.datetime "datetime.datetime") corresponding to the POSIX timestamp, with [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo")`None`. This may raise [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError"), if the timestamp is out of the range of values supported by the platform C `gmtime()` function, and [`OSError`](exceptions.xhtml#OSError "OSError") on `gmtime()` failure. It's common for this to be restricted to years in 1970 through 2038.
To get an aware [`datetime`](#datetime.datetime "datetime.datetime") object, call [`fromtimestamp()`](#datetime.datetime.fromtimestamp "datetime.datetime.fromtimestamp"):
```
datetime.fromtimestamp(timestamp, timezone.utc)
```
On the POSIX compliant platforms, it is equivalent to the following expression:
```
datetime(1970, 1, 1, tzinfo=timezone.utc) + timedelta(seconds=timestamp)
```
except the latter formula always supports the full years range: between [`MINYEAR`](#datetime.MINYEAR "datetime.MINYEAR") and [`MAXYEAR`](#datetime.MAXYEAR "datetime.MAXYEAR") inclusive.
在 3.3 版更改: Raise [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") instead of [`ValueError`](exceptions.xhtml#ValueError "ValueError") if the timestamp is out of the range of values supported by the platform C `gmtime()` function. Raise [`OSError`](exceptions.xhtml#OSError "OSError") instead of [`ValueError`](exceptions.xhtml#ValueError "ValueError") on `gmtime()` failure.
*classmethod* `datetime.``fromordinal`(*ordinal*)Return the [`datetime`](#datetime.datetime "datetime.datetime") corresponding to the proleptic Gregorian ordinal, where January 1 of year 1 has ordinal 1. [`ValueError`](exceptions.xhtml#ValueError "ValueError") is raised unless
```
1
<= ordinal <= datetime.max.toordinal()
```
. The hour, minute, second and microsecond of the result are all 0, and [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") is `None`.
*classmethod* `datetime.``combine`(*date*, *time*, *tzinfo=self.tzinfo*)Return a new [`datetime`](#datetime.datetime "datetime.datetime") object whose date components are equal to the given [`date`](#datetime.date "datetime.date") object's, and whose time components are equal to the given [`time`](#datetime.time "datetime.time") object's. If the *tzinfo*argument is provided, its value is used to set the [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attribute of the result, otherwise the [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo") attribute of the *time* argument is used.
For any [`datetime`](#datetime.datetime "datetime.datetime") object *d*, `d == datetime.combine(d.date(), d.time(), d.tzinfo)`. If date is a [`datetime`](#datetime.datetime "datetime.datetime") object, its time components and [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attributes are ignored.
在 3.6 版更改: Added the *tzinfo* argument.
*classmethod* `datetime.``fromisoformat`(*date\_string*)Return a [`datetime`](#module-datetime "datetime: Basic date and time types.") corresponding to a *date\_string* in one of the formats emitted by [`date.isoformat()`](#datetime.date.isoformat "datetime.date.isoformat") and [`datetime.isoformat()`](#datetime.datetime.isoformat "datetime.datetime.isoformat"). Specifically, this function supports strings in the format(s) `YYYY-MM-DD[*HH[:MM[:SS[.fff[fff]]]][+HH:MM[:SS[.ffffff]]]]`, where `*` can match any single character.
警告
This does not support parsing arbitrary ISO 8601 strings - it is only intended as the inverse operation of [`datetime.isoformat()`](#datetime.datetime.isoformat "datetime.datetime.isoformat").
3\.7 新版功能.
*classmethod* `datetime.``strptime`(*date\_string*, *format*)Return a [`datetime`](#datetime.datetime "datetime.datetime") corresponding to *date\_string*, parsed according to *format*. This is equivalent to
```
datetime(*(time.strptime(date_string,
format)[0:6]))
```
. [`ValueError`](exceptions.xhtml#ValueError "ValueError") is raised if the date\_string and format can't be parsed by [`time.strptime()`](time.xhtml#time.strptime "time.strptime") or if it returns a value which isn't a time tuple. For a complete list of formatting directives, see [strftime() and strptime() Behavior](#strftime-strptime-behavior).
Class attributes:
`datetime.``min`The earliest representable [`datetime`](#datetime.datetime "datetime.datetime"),
```
datetime(MINYEAR, 1, 1,
tzinfo=None)
```
.
`datetime.``max`The latest representable [`datetime`](#datetime.datetime "datetime.datetime"),
```
datetime(MAXYEAR, 12, 31, 23, 59,
59, 999999, tzinfo=None)
```
.
`datetime.``resolution`The smallest possible difference between non-equal [`datetime`](#datetime.datetime "datetime.datetime") objects, `timedelta(microseconds=1)`.
实例属性(只读):
`datetime.``year`Between [`MINYEAR`](#datetime.MINYEAR "datetime.MINYEAR") and [`MAXYEAR`](#datetime.MAXYEAR "datetime.MAXYEAR") inclusive.
`datetime.``month`1 至 12(含)
`datetime.``day`Between 1 and the number of days in the given month of the given year.
`datetime.``hour`In `range(24)`.
`datetime.``minute`In `range(60)`.
`datetime.``second`In `range(60)`.
`datetime.``microsecond`In `range(1000000)`.
`datetime.``tzinfo`The object passed as the *tzinfo* argument to the [`datetime`](#datetime.datetime "datetime.datetime") constructor, or `None` if none was passed.
`datetime.``fold`In `[0, 1]`. Used to disambiguate wall times during a repeated interval. (A repeated interval occurs when clocks are rolled back at the end of daylight saving time or when the UTC offset for the current zone is decreased for political reasons.) The value 0 (1) represents the earlier (later) of the two moments with the same wall time representation.
3\.6 新版功能.
支持的操作:
运算
结果
`datetime2 = datetime1 + timedelta`
(1)
`datetime2 = datetime1 - timedelta`
(2)
`timedelta = datetime1 - datetime2`
(3)
`datetime1 < datetime2`
Compares [`datetime`](#datetime.datetime "datetime.datetime") to [`datetime`](#datetime.datetime "datetime.datetime"). (4)
1. datetime2 is a duration of timedelta removed from datetime1, moving forward in time if `timedelta.days` > 0, or backward if `timedelta.days` < 0. The result has the same [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attribute as the input datetime, and datetime2 - datetime1 == timedelta after. [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") is raised if datetime2.year would be smaller than [`MINYEAR`](#datetime.MINYEAR "datetime.MINYEAR") or larger than [`MAXYEAR`](#datetime.MAXYEAR "datetime.MAXYEAR"). Note that no time zone adjustments are done even if the input is an aware object.
2. Computes the datetime2 such that datetime2 + timedelta == datetime1. As for addition, the result has the same [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attribute as the input datetime, and no time zone adjustments are done even if the input is aware.
3. Subtraction of a [`datetime`](#datetime.datetime "datetime.datetime") from a [`datetime`](#datetime.datetime "datetime.datetime") is defined only if both operands are naive, or if both are aware. If one is aware and the other is naive, [`TypeError`](exceptions.xhtml#TypeError "TypeError") is raised.
If both are naive, or both are aware and have the same [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attribute, the [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attributes are ignored, and the result is a [`timedelta`](#datetime.timedelta "datetime.timedelta")object *t* such that `datetime2 + t == datetime1`. No time zone adjustments are done in this case.
If both are aware and have different [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attributes, `a-b` acts as if *a* and *b* were first converted to naive UTC datetimes first. The result is
```
(a.replace(tzinfo=None) - a.utcoffset()) - (b.replace(tzinfo=None)
\- b.utcoffset())
```
except that the implementation never overflows.
4. *datetime1* is considered less than *datetime2* when *datetime1* precedes *datetime2* in time.
If one comparand is naive and the other is aware, [`TypeError`](exceptions.xhtml#TypeError "TypeError")is raised if an order comparison is attempted. For equality comparisons, naive instances are never equal to aware instances.
If both comparands are aware, and have the same [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attribute, the common [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attribute is ignored and the base datetimes are compared. If both comparands are aware and have different [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo")attributes, the comparands are first adjusted by subtracting their UTC offsets (obtained from `self.utcoffset()`).
在 3.3 版更改: Equality comparisons between naive and aware [`datetime`](#datetime.datetime "datetime.datetime")instances don't raise [`TypeError`](exceptions.xhtml#TypeError "TypeError").
注解
In order to stop comparison from falling back to the default scheme of comparing object addresses, datetime comparison normally raises [`TypeError`](exceptions.xhtml#TypeError "TypeError") if the other comparand isn't also a [`datetime`](#datetime.datetime "datetime.datetime") object. However, `NotImplemented` is returned instead if the other comparand has a `timetuple()` attribute. This hook gives other kinds of date objects a chance at implementing mixed-type comparison. If not, when a [`datetime`](#datetime.datetime "datetime.datetime")object is compared to an object of a different type, [`TypeError`](exceptions.xhtml#TypeError "TypeError") is raised unless the comparison is `==` or `!=`. The latter cases return [`False`](constants.xhtml#False "False") or [`True`](constants.xhtml#True "True"), respectively.
[`datetime`](#datetime.datetime "datetime.datetime") objects can be used as dictionary keys. In Boolean contexts, all [`datetime`](#datetime.datetime "datetime.datetime") objects are considered to be true.
Instance methods:
`datetime.``date`()Return [`date`](#datetime.date "datetime.date") object with same year, month and day.
`datetime.``time`()Return [`time`](#datetime.time "datetime.time") object with same hour, minute, second, microsecond and fold. [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") is `None`. See also method [`timetz()`](#datetime.datetime.timetz "datetime.datetime.timetz").
在 3.6 版更改: The fold value is copied to the returned [`time`](#datetime.time "datetime.time") object.
`datetime.``timetz`()Return [`time`](#datetime.time "datetime.time") object with same hour, minute, second, microsecond, fold, and tzinfo attributes. See also method [`time()`](time.xhtml#module-time "time: Time access and conversions.").
在 3.6 版更改: The fold value is copied to the returned [`time`](#datetime.time "datetime.time") object.
`datetime.``replace`(*year=self.year*, *month=self.month*, *day=self.day*, *hour=self.hour*, *minute=self.minute*, *second=self.second*, *microsecond=self.microsecond*, *tzinfo=self.tzinfo*, *\* fold=0*)Return a datetime with the same attributes, except for those attributes given new values by whichever keyword arguments are specified. Note that `tzinfo=None` can be specified to create a naive datetime from an aware datetime with no conversion of date and time data.
3\.6 新版功能: Added the `fold` argument.
`datetime.``astimezone`(*tz=None*)Return a [`datetime`](#datetime.datetime "datetime.datetime") object with new [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") attribute *tz*, adjusting the date and time data so the result is the same UTC time as *self*, but in *tz*'s local time.
If provided, *tz* must be an instance of a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass, and its [`utcoffset()`](#datetime.datetime.utcoffset "datetime.datetime.utcoffset") and [`dst()`](#datetime.datetime.dst "datetime.datetime.dst") methods must not return `None`. If *self*is naive, it is presumed to represent time in the system timezone.
If called without arguments (or with `tz=None`) the system local timezone is assumed for the target timezone. The `.tzinfo` attribute of the converted datetime instance will be set to an instance of [`timezone`](#datetime.timezone "datetime.timezone")with the zone name and offset obtained from the OS.
If `self.tzinfo` is *tz*, `self.astimezone(tz)` is equal to *self*: no adjustment of date or time data is performed. Else the result is local time in the timezone *tz*, representing the same UTC time as *self*: after `astz = dt.astimezone(tz)`, `astz - astz.utcoffset()` will have the same date and time data as `dt - dt.utcoffset()`.
If you merely want to attach a time zone object *tz* to a datetime *dt* without adjustment of date and time data, use `dt.replace(tzinfo=tz)`. If you merely want to remove the time zone object from an aware datetime *dt* without conversion of date and time data, use `dt.replace(tzinfo=None)`.
Note that the default [`tzinfo.fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc") method can be overridden in a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass to affect the result returned by [`astimezone()`](#datetime.datetime.astimezone "datetime.datetime.astimezone"). Ignoring error cases, [`astimezone()`](#datetime.datetime.astimezone "datetime.datetime.astimezone") acts like:
```
def astimezone(self, tz):
if self.tzinfo is tz:
return self
# Convert self to UTC, and attach the new time zone object.
utc = (self - self.utcoffset()).replace(tzinfo=tz)
# Convert from UTC to tz's local time.
return tz.fromutc(utc)
```
在 3.3 版更改: *tz* now can be omitted.
在 3.6 版更改: The [`astimezone()`](#datetime.datetime.astimezone "datetime.datetime.astimezone") method can now be called on naive instances that are presumed to represent system local time.
`datetime.``utcoffset`()If [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") is `None`, returns `None`, else returns `self.tzinfo.utcoffset(self)`, and raises an exception if the latter doesn't return `None` or a [`timedelta`](#datetime.timedelta "datetime.timedelta") object with magnitude less than one day.
在 3.7 版更改: The UTC offset is not restricted to a whole number of minutes.
`datetime.``dst`()If [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") is `None`, returns `None`, else returns `self.tzinfo.dst(self)`, and raises an exception if the latter doesn't return `None` or a [`timedelta`](#datetime.timedelta "datetime.timedelta") object with magnitude less than one day.
在 3.7 版更改: The DST offset is not restricted to a whole number of minutes.
`datetime.``tzname`()If [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") is `None`, returns `None`, else returns `self.tzinfo.tzname(self)`, raises an exception if the latter doesn't return `None` or a string object,
`datetime.``timetuple`()Return a [`time.struct_time`](time.xhtml#time.struct_time "time.struct_time") such as returned by [`time.localtime()`](time.xhtml#time.localtime "time.localtime"). `d.timetuple()` is equivalent to
```
time.struct_time((d.year, d.month, d.day,
d.hour, d.minute, d.second, d.weekday(), yday, dst))
```
, where
```
yday =
d.toordinal() - date(d.year, 1, 1).toordinal() + 1
```
is the day number within the current year starting with `1` for January 1st. The `tm_isdst` flag of the result is set according to the [`dst()`](#datetime.datetime.dst "datetime.datetime.dst") method: [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo") is `None` or [`dst()`](#datetime.datetime.dst "datetime.datetime.dst") returns `None`, `tm_isdst` is set to `-1`; else if [`dst()`](#datetime.datetime.dst "datetime.datetime.dst") returns a non-zero value, `tm_isdst` is set to `1`; else `tm_isdst` is set to `0`.
`datetime.``utctimetuple`()If [`datetime`](#datetime.datetime "datetime.datetime") instance *d* is naive, this is the same as `d.timetuple()` except that `tm_isdst` is forced to 0 regardless of what `d.dst()` returns. DST is never in effect for a UTC time.
If *d* is aware, *d* is normalized to UTC time, by subtracting `d.utcoffset()`, and a [`time.struct_time`](time.xhtml#time.struct_time "time.struct_time") for the normalized time is returned. `tm_isdst` is forced to 0. Note that an [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") may be raised if *d*.year was `MINYEAR` or `MAXYEAR` and UTC adjustment spills over a year boundary.
`datetime.``toordinal`()Return the proleptic Gregorian ordinal of the date. The same as `self.date().toordinal()`.
`datetime.``timestamp`()Return POSIX timestamp corresponding to the [`datetime`](#datetime.datetime "datetime.datetime")instance. The return value is a [`float`](functions.xhtml#float "float") similar to that returned by [`time.time()`](time.xhtml#time.time "time.time").
Naive [`datetime`](#datetime.datetime "datetime.datetime") instances are assumed to represent local time and this method relies on the platform C `mktime()`function to perform the conversion. Since [`datetime`](#datetime.datetime "datetime.datetime")supports wider range of values than `mktime()` on many platforms, this method may raise [`OverflowError`](exceptions.xhtml#OverflowError "OverflowError") for times far in the past or far in the future.
For aware [`datetime`](#datetime.datetime "datetime.datetime") instances, the return value is computed as:
```
(dt - datetime(1970, 1, 1, tzinfo=timezone.utc)).total_seconds()
```
3\.3 新版功能.
在 3.6 版更改: The [`timestamp()`](#datetime.datetime.timestamp "datetime.datetime.timestamp") method uses the [`fold`](#datetime.datetime.fold "datetime.datetime.fold") attribute to disambiguate the times during a repeated interval.
注解
There is no method to obtain the POSIX timestamp directly from a naive [`datetime`](#datetime.datetime "datetime.datetime") instance representing UTC time. If your application uses this convention and your system timezone is not set to UTC, you can obtain the POSIX timestamp by supplying `tzinfo=timezone.utc`:
```
timestamp = dt.replace(tzinfo=timezone.utc).timestamp()
```
or by calculating the timestamp directly:
```
timestamp = (dt - datetime(1970, 1, 1)) / timedelta(seconds=1)
```
`datetime.``weekday`()Return the day of the week as an integer, where Monday is 0 and Sunday is 6. The same as `self.date().weekday()`. See also [`isoweekday()`](#datetime.datetime.isoweekday "datetime.datetime.isoweekday").
`datetime.``isoweekday`()Return the day of the week as an integer, where Monday is 1 and Sunday is 7. The same as `self.date().isoweekday()`. See also [`weekday()`](#datetime.datetime.weekday "datetime.datetime.weekday"), [`isocalendar()`](#datetime.datetime.isocalendar "datetime.datetime.isocalendar").
`datetime.``isocalendar`()Return a 3-tuple, (ISO year, ISO week number, ISO weekday). The same as `self.date().isocalendar()`.
`datetime.``isoformat`(*sep='T'*, *timespec='auto'*)Return a string representing the date and time in ISO 8601 format, YYYY-MM-DDTHH:MM:SS.ffffff or, if [`microsecond`](#datetime.datetime.microsecond "datetime.datetime.microsecond") is 0, YYYY-MM-DDTHH:MM:SS
If [`utcoffset()`](#datetime.datetime.utcoffset "datetime.datetime.utcoffset") does not return `None`, a string is appended, giving the UTC offset: YYYY-MM-DDTHH:MM:SS.ffffff+HH:MM\[:SS\[.ffffff\]\] or, if [`microsecond`](#datetime.datetime.microsecond "datetime.datetime.microsecond")is 0 YYYY-MM-DDTHH:MM:SS+HH:MM\[:SS\[.ffffff\]\].
The optional argument *sep* (default `'T'`) is a one-character separator, placed between the date and time portions of the result. For example,
```
>>> from datetime import tzinfo, timedelta, datetime
>>> class TZ(tzinfo):
... def utcoffset(self, dt): return timedelta(minutes=-399)
...
>>> datetime(2002, 12, 25, tzinfo=TZ()).isoformat(' ')
'2002-12-25 00:00:00-06:39'
```
The optional argument *timespec* specifies the number of additional components of the time to include (the default is `'auto'`). It can be one of the following:
- `'auto'`: Same as `'seconds'` if [`microsecond`](#datetime.datetime.microsecond "datetime.datetime.microsecond") is 0, same as `'microseconds'` otherwise.
- `'hours'`: Include the [`hour`](#datetime.datetime.hour "datetime.datetime.hour") in the two-digit HH format.
- `'minutes'`: Include [`hour`](#datetime.datetime.hour "datetime.datetime.hour") and [`minute`](#datetime.datetime.minute "datetime.datetime.minute") in HH:MM format.
- `'seconds'`: Include [`hour`](#datetime.datetime.hour "datetime.datetime.hour"), [`minute`](#datetime.datetime.minute "datetime.datetime.minute"), and [`second`](#datetime.datetime.second "datetime.datetime.second")in HH:MM:SS format.
- `'milliseconds'`: Include full time, but truncate fractional second part to milliseconds. HH:MM:SS.sss format.
- `'microseconds'`: Include full time in HH:MM:SS.ffffff format.
注解
Excluded time components are truncated, not rounded.
[`ValueError`](exceptions.xhtml#ValueError "ValueError") will be raised on an invalid *timespec* argument.
```
>>> from datetime import datetime
>>> datetime.now().isoformat(timespec='minutes') # doctest: +SKIP
'2002-12-25T00:00'
>>> dt = datetime(2015, 1, 1, 12, 30, 59, 0)
>>> dt.isoformat(timespec='microseconds')
'2015-01-01T12:30:59.000000'
```
3\.6 新版功能: Added the *timespec* argument.
`datetime.``__str__`()For a [`datetime`](#datetime.datetime "datetime.datetime") instance *d*, `str(d)` is equivalent to `d.isoformat(' ')`.
`datetime.``ctime`()Return a string representing the date and time, for example
```
datetime(2002, 12,
4, 20, 30, 40).ctime() == 'Wed Dec 4 20:30:40 2002'
```
. `d.ctime()` is equivalent to `time.ctime(time.mktime(d.timetuple()))` on platforms where the native C `ctime()` function (which [`time.ctime()`](time.xhtml#time.ctime "time.ctime") invokes, but which [`datetime.ctime()`](#datetime.datetime.ctime "datetime.datetime.ctime") does not invoke) conforms to the C standard.
`datetime.``strftime`(*format*)Return a string representing the date and time, controlled by an explicit format string. For a complete list of formatting directives, see [strftime() and strptime() Behavior](#strftime-strptime-behavior).
`datetime.``__format__`(*format*)Same as [`datetime.strftime()`](#datetime.datetime.strftime "datetime.datetime.strftime"). This makes it possible to specify a format string for a [`datetime`](#datetime.datetime "datetime.datetime") object in [formatted string literals](../reference/lexical_analysis.xhtml#f-strings) and when using [`str.format()`](stdtypes.xhtml#str.format "str.format"). For a complete list of formatting directives, see [strftime() and strptime() Behavior](#strftime-strptime-behavior).
Examples of working with datetime objects:
```
>>> from datetime import datetime, date, time
>>> # Using datetime.combine()
>>> d = date(2005, 7, 14)
>>> t = time(12, 30)
>>> datetime.combine(d, t)
datetime.datetime(2005, 7, 14, 12, 30)
>>> # Using datetime.now() or datetime.utcnow()
>>> datetime.now()
datetime.datetime(2007, 12, 6, 16, 29, 43, 79043) # GMT +1
>>> datetime.utcnow()
datetime.datetime(2007, 12, 6, 15, 29, 43, 79060)
>>> # Using datetime.strptime()
>>> dt = datetime.strptime("21/11/06 16:30", "%d/%m/%y %H:%M")
>>> dt
datetime.datetime(2006, 11, 21, 16, 30)
>>> # Using datetime.timetuple() to get tuple of all attributes
>>> tt = dt.timetuple()
>>> for it in tt:
... print(it)
...
2006 # year
11 # month
21 # day
16 # hour
30 # minute
0 # second
1 # weekday (0 = Monday)
325 # number of days since 1st January
-1 # dst - method tzinfo.dst() returned None
>>> # Date in ISO format
>>> ic = dt.isocalendar()
>>> for it in ic:
... print(it)
...
2006 # ISO year
47 # ISO week
2 # ISO weekday
>>> # Formatting datetime
>>> dt.strftime("%A, %d. %B %Y %I:%M%p")
'Tuesday, 21. November 2006 04:30PM'
>>> 'The {1} is {0:%d}, the {2} is {0:%B}, the {3} is {0:%I:%M%p}.'.format(dt, "day", "month", "time")
'The day is 21, the month is November, the time is 04:30PM.'
```
Using datetime with tzinfo:
```
>>> from datetime import timedelta, datetime, tzinfo
>>> class GMT1(tzinfo):
... def utcoffset(self, dt):
... return timedelta(hours=1) + self.dst(dt)
... def dst(self, dt):
... # DST starts last Sunday in March
... d = datetime(dt.year, 4, 1) # ends last Sunday in October
... self.dston = d - timedelta(days=d.weekday() + 1)
... d = datetime(dt.year, 11, 1)
... self.dstoff = d - timedelta(days=d.weekday() + 1)
... if self.dston <= dt.replace(tzinfo=None) < self.dstoff:
... return timedelta(hours=1)
... else:
... return timedelta(0)
... def tzname(self,dt):
... return "GMT +1"
...
>>> class GMT2(tzinfo):
... def utcoffset(self, dt):
... return timedelta(hours=2) + self.dst(dt)
... def dst(self, dt):
... d = datetime(dt.year, 4, 1)
... self.dston = d - timedelta(days=d.weekday() + 1)
... d = datetime(dt.year, 11, 1)
... self.dstoff = d - timedelta(days=d.weekday() + 1)
... if self.dston <= dt.replace(tzinfo=None) < self.dstoff:
... return timedelta(hours=1)
... else:
... return timedelta(0)
... def tzname(self,dt):
... return "GMT +2"
...
>>> gmt1 = GMT1()
>>> # Daylight Saving Time
>>> dt1 = datetime(2006, 11, 21, 16, 30, tzinfo=gmt1)
>>> dt1.dst()
datetime.timedelta(0)
>>> dt1.utcoffset()
datetime.timedelta(seconds=3600)
>>> dt2 = datetime(2006, 6, 14, 13, 0, tzinfo=gmt1)
>>> dt2.dst()
datetime.timedelta(seconds=3600)
>>> dt2.utcoffset()
datetime.timedelta(seconds=7200)
>>> # Convert datetime to another time zone
>>> dt3 = dt2.astimezone(GMT2())
>>> dt3 # doctest: +ELLIPSIS
datetime.datetime(2006, 6, 14, 14, 0, tzinfo=<GMT2 object at 0x...>)
>>> dt2 # doctest: +ELLIPSIS
datetime.datetime(2006, 6, 14, 13, 0, tzinfo=<GMT1 object at 0x...>)
>>> dt2.utctimetuple() == dt3.utctimetuple()
True
```
## [`time`](#datetime.time "datetime.time") Objects
A time object represents a (local) time of day, independent of any particular day, and subject to adjustment via a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") object.
*class* `datetime.``time`(*hour=0*, *minute=0*, *second=0*, *microsecond=0*, *tzinfo=None*, *\**, *fold=0*)All arguments are optional. *tzinfo* may be `None`, or an instance of a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass. The remaining arguments may be integers, in the following ranges:
- `0 <= hour < 24`,
- `0 <= minute < 60`,
- `0 <= second < 60`,
- `0 <= microsecond < 1000000`,
- `fold in [0, 1]`.
If an argument outside those ranges is given, [`ValueError`](exceptions.xhtml#ValueError "ValueError") is raised. All default to `0` except *tzinfo*, which defaults to [`None`](constants.xhtml#None "None").
Class attributes:
`time.``min`The earliest representable [`time`](#datetime.time "datetime.time"), `time(0, 0, 0, 0)`.
`time.``max`The latest representable [`time`](#datetime.time "datetime.time"), `time(23, 59, 59, 999999)`.
`time.``resolution`The smallest possible difference between non-equal [`time`](#datetime.time "datetime.time") objects, `timedelta(microseconds=1)`, although note that arithmetic on [`time`](#datetime.time "datetime.time") objects is not supported.
实例属性(只读):
`time.``hour`In `range(24)`.
`time.``minute`In `range(60)`.
`time.``second`In `range(60)`.
`time.``microsecond`In `range(1000000)`.
`time.``tzinfo`The object passed as the tzinfo argument to the [`time`](#datetime.time "datetime.time") constructor, or `None` if none was passed.
`time.``fold`In `[0, 1]`. Used to disambiguate wall times during a repeated interval. (A repeated interval occurs when clocks are rolled back at the end of daylight saving time or when the UTC offset for the current zone is decreased for political reasons.) The value 0 (1) represents the earlier (later) of the two moments with the same wall time representation.
3\.6 新版功能.
支持的操作:
- comparison of [`time`](#datetime.time "datetime.time") to [`time`](#datetime.time "datetime.time"), where *a* is considered less than *b* when *a* precedes *b* in time. If one comparand is naive and the other is aware, [`TypeError`](exceptions.xhtml#TypeError "TypeError") is raised if an order comparison is attempted. For equality comparisons, naive instances are never equal to aware instances.
If both comparands are aware, and have the same [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo") attribute, the common [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo") attribute is ignored and the base times are compared. If both comparands are aware and have different [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo") attributes, the comparands are first adjusted by subtracting their UTC offsets (obtained from `self.utcoffset()`). In order to stop mixed-type comparisons from falling back to the default comparison by object address, when a [`time`](#datetime.time "datetime.time") object is compared to an object of a different type, [`TypeError`](exceptions.xhtml#TypeError "TypeError") is raised unless the comparison is `==` or `!=`. The latter cases return [`False`](constants.xhtml#False "False") or [`True`](constants.xhtml#True "True"), respectively.
在 3.3 版更改: Equality comparisons between naive and aware [`time`](#datetime.time "datetime.time") instances don't raise [`TypeError`](exceptions.xhtml#TypeError "TypeError").
- hash, use as dict key
- efficient pickling
In boolean contexts, a [`time`](#datetime.time "datetime.time") object is always considered to be true.
在 3.5 版更改: Before Python 3.5, a [`time`](#datetime.time "datetime.time") object was considered to be false if it represented midnight in UTC. This behavior was considered obscure and error-prone and has been removed in Python 3.5. See [bpo-13936](https://bugs.python.org/issue13936) \[https://bugs.python.org/issue13936\] for full details.
Other constructor:
*classmethod* `time.``fromisoformat`(*time\_string*)Return a [`time`](time.xhtml#module-time "time: Time access and conversions.") corresponding to a *time\_string* in one of the formats emitted by [`time.isoformat()`](#datetime.time.isoformat "datetime.time.isoformat"). Specifically, this function supports strings in the format(s) `HH[:MM[:SS[.fff[fff]]]][+HH:MM[:SS[.ffffff]]]`.
警告
This does not support parsing arbitrary ISO 8601 strings - it is only intended as the inverse operation of [`time.isoformat()`](#datetime.time.isoformat "datetime.time.isoformat").
3\.7 新版功能.
Instance methods:
`time.``replace`(*hour=self.hour*, *minute=self.minute*, *second=self.second*, *microsecond=self.microsecond*, *tzinfo=self.tzinfo*, *\* fold=0*)Return a [`time`](#datetime.time "datetime.time") with the same value, except for those attributes given new values by whichever keyword arguments are specified. Note that `tzinfo=None` can be specified to create a naive [`time`](#datetime.time "datetime.time") from an aware [`time`](#datetime.time "datetime.time"), without conversion of the time data.
3\.6 新版功能: Added the `fold` argument.
`time.``isoformat`(*timespec='auto'*)Return a string representing the time in ISO 8601 format, HH:MM:SS.ffffff or, if [`microsecond`](#datetime.time.microsecond "datetime.time.microsecond") is 0, HH:MM:SS If [`utcoffset()`](#datetime.time.utcoffset "datetime.time.utcoffset") does not return `None`, a string is appended, giving the UTC offset: HH:MM:SS.ffffff+HH:MM\[:SS\[.ffffff\]\] or, if self.microsecond is 0, HH:MM:SS+HH:MM\[:SS\[.ffffff\]\].
The optional argument *timespec* specifies the number of additional components of the time to include (the default is `'auto'`). It can be one of the following:
- `'auto'`: Same as `'seconds'` if [`microsecond`](#datetime.time.microsecond "datetime.time.microsecond") is 0, same as `'microseconds'` otherwise.
- `'hours'`: Include the [`hour`](#datetime.time.hour "datetime.time.hour") in the two-digit HH format.
- `'minutes'`: Include [`hour`](#datetime.time.hour "datetime.time.hour") and [`minute`](#datetime.time.minute "datetime.time.minute") in HH:MM format.
- `'seconds'`: Include [`hour`](#datetime.time.hour "datetime.time.hour"), [`minute`](#datetime.time.minute "datetime.time.minute"), and [`second`](#datetime.time.second "datetime.time.second")in HH:MM:SS format.
- `'milliseconds'`: Include full time, but truncate fractional second part to milliseconds. HH:MM:SS.sss format.
- `'microseconds'`: Include full time in HH:MM:SS.ffffff format.
注解
Excluded time components are truncated, not rounded.
[`ValueError`](exceptions.xhtml#ValueError "ValueError") will be raised on an invalid *timespec* argument.
```
>>> from datetime import time
>>> time(hour=12, minute=34, second=56, microsecond=123456).isoformat(timespec='minutes')
'12:34'
>>> dt = time(hour=12, minute=34, second=56, microsecond=0)
>>> dt.isoformat(timespec='microseconds')
'12:34:56.000000'
>>> dt.isoformat(timespec='auto')
'12:34:56'
```
3\.6 新版功能: Added the *timespec* argument.
`time.``__str__`()For a time *t*, `str(t)` is equivalent to `t.isoformat()`.
`time.``strftime`(*format*)Return a string representing the time, controlled by an explicit format string. For a complete list of formatting directives, see [strftime() and strptime() Behavior](#strftime-strptime-behavior).
`time.``__format__`(*format*)Same as [`time.strftime()`](#datetime.time.strftime "datetime.time.strftime"). This makes it possible to specify a format string for a [`time`](#datetime.time "datetime.time") object in [formatted string literals](../reference/lexical_analysis.xhtml#f-strings) and when using [`str.format()`](stdtypes.xhtml#str.format "str.format"). For a complete list of formatting directives, see [strftime() and strptime() Behavior](#strftime-strptime-behavior).
`time.``utcoffset`()If [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo") is `None`, returns `None`, else returns `self.tzinfo.utcoffset(None)`, and raises an exception if the latter doesn't return `None` or a [`timedelta`](#datetime.timedelta "datetime.timedelta") object with magnitude less than one day.
在 3.7 版更改: The UTC offset is not restricted to a whole number of minutes.
`time.``dst`()If [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo") is `None`, returns `None`, else returns `self.tzinfo.dst(None)`, and raises an exception if the latter doesn't return `None`, or a [`timedelta`](#datetime.timedelta "datetime.timedelta") object with magnitude less than one day.
在 3.7 版更改: The DST offset is not restricted to a whole number of minutes.
`time.``tzname`()If [`tzinfo`](#datetime.time.tzinfo "datetime.time.tzinfo") is `None`, returns `None`, else returns `self.tzinfo.tzname(None)`, or raises an exception if the latter doesn't return `None` or a string object.
示例:
```
>>> from datetime import time, tzinfo, timedelta
>>> class GMT1(tzinfo):
... def utcoffset(self, dt):
... return timedelta(hours=1)
... def dst(self, dt):
... return timedelta(0)
... def tzname(self,dt):
... return "Europe/Prague"
...
>>> t = time(12, 10, 30, tzinfo=GMT1())
>>> t # doctest: +ELLIPSIS
datetime.time(12, 10, 30, tzinfo=<GMT1 object at 0x...>)
>>> gmt = GMT1()
>>> t.isoformat()
'12:10:30+01:00'
>>> t.dst()
datetime.timedelta(0)
>>> t.tzname()
'Europe/Prague'
>>> t.strftime("%H:%M:%S %Z")
'12:10:30 Europe/Prague'
>>> 'The {} is {:%H:%M}.'.format("time", t)
'The time is 12:10.'
```
## [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") 对象
*class* `datetime.``tzinfo`This is an abstract base class, meaning that this class should not be instantiated directly. You need to derive a concrete subclass, and (at least) supply implementations of the standard [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") methods needed by the [`datetime`](#datetime.datetime "datetime.datetime") methods you use. The [`datetime`](#module-datetime "datetime: Basic date and time types.") module supplies a simple concrete subclass of [`tzinfo`](#datetime.tzinfo "datetime.tzinfo"), [`timezone`](#datetime.timezone "datetime.timezone"), which can represent timezones with fixed offset from UTC such as UTC itself or North American EST and EDT.
An instance of (a concrete subclass of) [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") can be passed to the constructors for [`datetime`](#datetime.datetime "datetime.datetime") and [`time`](#datetime.time "datetime.time") objects. The latter objects view their attributes as being in local time, and the [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") object supports methods revealing offset of local time from UTC, the name of the time zone, and DST offset, all relative to a date or time object passed to them.
Special requirement for pickling: A [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass must have an [`__init__()`](../reference/datamodel.xhtml#object.__init__ "object.__init__") method that can be called with no arguments, else it can be pickled but possibly not unpickled again. This is a technical requirement that may be relaxed in the future.
A concrete subclass of [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") may need to implement the following methods. Exactly which methods are needed depends on the uses made of aware [`datetime`](#module-datetime "datetime: Basic date and time types.") objects. If in doubt, simply implement all of them.
`tzinfo.``utcoffset`(*dt*)Return offset of local time from UTC, as a [`timedelta`](#datetime.timedelta "datetime.timedelta") object that is positive east of UTC. If local time is west of UTC, this should be negative. Note that this is intended to be the total offset from UTC; for example, if a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") object represents both time zone and DST adjustments, [`utcoffset()`](#datetime.tzinfo.utcoffset "datetime.tzinfo.utcoffset") should return their sum. If the UTC offset isn't known, return `None`. Else the value returned must be a [`timedelta`](#datetime.timedelta "datetime.timedelta") object strictly between `-timedelta(hours=24)` and `timedelta(hours=24)` (the magnitude of the offset must be less than one day). Most implementations of [`utcoffset()`](#datetime.tzinfo.utcoffset "datetime.tzinfo.utcoffset") will probably look like one of these two:
```
return CONSTANT # fixed-offset class
return CONSTANT + self.dst(dt) # daylight-aware class
```
If [`utcoffset()`](#datetime.tzinfo.utcoffset "datetime.tzinfo.utcoffset") does not return `None`, [`dst()`](#datetime.tzinfo.dst "datetime.tzinfo.dst") should not return `None` either.
The default implementation of [`utcoffset()`](#datetime.tzinfo.utcoffset "datetime.tzinfo.utcoffset") raises [`NotImplementedError`](exceptions.xhtml#NotImplementedError "NotImplementedError").
在 3.7 版更改: The UTC offset is not restricted to a whole number of minutes.
`tzinfo.``dst`(*dt*)Return the daylight saving time (DST) adjustment, as a [`timedelta`](#datetime.timedelta "datetime.timedelta")object or `None` if DST information isn't known. Return `timedelta(0)` if DST is not in effect. If DST is in effect, return the offset as a [`timedelta`](#datetime.timedelta "datetime.timedelta") object (see [`utcoffset()`](#datetime.tzinfo.utcoffset "datetime.tzinfo.utcoffset") for details). Note that DST offset, if applicable, has already been added to the UTC offset returned by [`utcoffset()`](#datetime.tzinfo.utcoffset "datetime.tzinfo.utcoffset"), so there's no need to consult [`dst()`](#datetime.tzinfo.dst "datetime.tzinfo.dst") unless you're interested in obtaining DST info separately. For example, [`datetime.timetuple()`](#datetime.datetime.timetuple "datetime.datetime.timetuple") calls its [`tzinfo`](#datetime.datetime.tzinfo "datetime.datetime.tzinfo")attribute's [`dst()`](#datetime.tzinfo.dst "datetime.tzinfo.dst") method to determine how the `tm_isdst` flag should be set, and [`tzinfo.fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc") calls [`dst()`](#datetime.tzinfo.dst "datetime.tzinfo.dst") to account for DST changes when crossing time zones.
An instance *tz* of a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass that models both standard and daylight times must be consistent in this sense:
`tz.utcoffset(dt) - tz.dst(dt)`
must return the same result for every [`datetime`](#datetime.datetime "datetime.datetime") *dt* with
```
dt.tzinfo ==
tz
```
For sane [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclasses, this expression yields the time zone's "standard offset", which should not depend on the date or the time, but only on geographic location. The implementation of [`datetime.astimezone()`](#datetime.datetime.astimezone "datetime.datetime.astimezone")relies on this, but cannot detect violations; it's the programmer's responsibility to ensure it. If a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass cannot guarantee this, it may be able to override the default implementation of [`tzinfo.fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc") to work correctly with `astimezone()` regardless.
Most implementations of [`dst()`](#datetime.tzinfo.dst "datetime.tzinfo.dst") will probably look like one of these two:
```
def dst(self, dt):
# a fixed-offset class: doesn't account for DST
return timedelta(0)
```
or
```
def dst(self, dt):
# Code to set dston and dstoff to the time zone's DST
# transition times based on the input dt.year, and expressed
# in standard local time. Then
if dston <= dt.replace(tzinfo=None) < dstoff:
return timedelta(hours=1)
else:
return timedelta(0)
```
The default implementation of [`dst()`](#datetime.tzinfo.dst "datetime.tzinfo.dst") raises [`NotImplementedError`](exceptions.xhtml#NotImplementedError "NotImplementedError").
在 3.7 版更改: The DST offset is not restricted to a whole number of minutes.
`tzinfo.``tzname`(*dt*)Return the time zone name corresponding to the [`datetime`](#datetime.datetime "datetime.datetime") object *dt*, as a string. Nothing about string names is defined by the [`datetime`](#module-datetime "datetime: Basic date and time types.") module, and there's no requirement that it mean anything in particular. For example, "GMT", "UTC", "-500", "-5:00", "EDT", "US/Eastern", "America/New York" are all valid replies. Return `None` if a string name isn't known. Note that this is a method rather than a fixed string primarily because some [`tzinfo`](#datetime.tzinfo "datetime.tzinfo")subclasses will wish to return different names depending on the specific value of *dt* passed, especially if the [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") class is accounting for daylight time.
The default implementation of [`tzname()`](#datetime.tzinfo.tzname "datetime.tzinfo.tzname") raises [`NotImplementedError`](exceptions.xhtml#NotImplementedError "NotImplementedError").
These methods are called by a [`datetime`](#datetime.datetime "datetime.datetime") or [`time`](#datetime.time "datetime.time") object, in response to their methods of the same names. A [`datetime`](#datetime.datetime "datetime.datetime") object passes itself as the argument, and a [`time`](#datetime.time "datetime.time") object passes `None` as the argument. A [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass's methods should therefore be prepared to accept a *dt* argument of `None`, or of class [`datetime`](#datetime.datetime "datetime.datetime").
When `None` is passed, it's up to the class designer to decide the best response. For example, returning `None` is appropriate if the class wishes to say that time objects don't participate in the [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") protocols. It may be more useful for `utcoffset(None)` to return the standard UTC offset, as there is no other convention for discovering the standard offset.
When a [`datetime`](#datetime.datetime "datetime.datetime") object is passed in response to a [`datetime`](#datetime.datetime "datetime.datetime")method, `dt.tzinfo` is the same object as *self*. [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") methods can rely on this, unless user code calls [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") methods directly. The intent is that the [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") methods interpret *dt* as being in local time, and not need worry about objects in other timezones.
There is one more [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") method that a subclass may wish to override:
`tzinfo.``fromutc`(*dt*)This is called from the default [`datetime.astimezone()`](#datetime.datetime.astimezone "datetime.datetime.astimezone")implementation. When called from that, `dt.tzinfo` is *self*, and *dt*'s date and time data are to be viewed as expressing a UTC time. The purpose of [`fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc") is to adjust the date and time data, returning an equivalent datetime in *self*'s local time.
Most [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclasses should be able to inherit the default [`fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc") implementation without problems. It's strong enough to handle fixed-offset time zones, and time zones accounting for both standard and daylight time, and the latter even if the DST transition times differ in different years. An example of a time zone the default [`fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc")implementation may not handle correctly in all cases is one where the standard offset (from UTC) depends on the specific date and time passed, which can happen for political reasons. The default implementations of `astimezone()` and [`fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc") may not produce the result you want if the result is one of the hours straddling the moment the standard offset changes.
Skipping code for error cases, the default [`fromutc()`](#datetime.tzinfo.fromutc "datetime.tzinfo.fromutc") implementation acts like:
```
def fromutc(self, dt):
# raise ValueError error if dt.tzinfo is not self
dtoff = dt.utcoffset()
dtdst = dt.dst()
# raise ValueError if dtoff is None or dtdst is None
delta = dtoff - dtdst # this is self's standard offset
if delta:
dt += delta # convert to standard local time
dtdst = dt.dst()
# raise ValueError if dtdst is None
if dtdst:
return dt + dtdst
else:
return dt
```
In the following `tzinfo_examples.py` file there are some examples of [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") classes:
```
from datetime import tzinfo, timedelta, datetime
ZERO = timedelta(0)
HOUR = timedelta(hours=1)
SECOND = timedelta(seconds=1)
# A class capturing the platform's idea of local time.
# (May result in wrong values on historical times in
# timezones where UTC offset and/or the DST rules had
# changed in the past.)
import time as _time
STDOFFSET = timedelta(seconds = -_time.timezone)
if _time.daylight:
DSTOFFSET = timedelta(seconds = -_time.altzone)
else:
DSTOFFSET = STDOFFSET
DSTDIFF = DSTOFFSET - STDOFFSET
class LocalTimezone(tzinfo):
def fromutc(self, dt):
assert dt.tzinfo is self
stamp = (dt - datetime(1970, 1, 1, tzinfo=self)) // SECOND
args = _time.localtime(stamp)[:6]
dst_diff = DSTDIFF // SECOND
# Detect fold
fold = (args == _time.localtime(stamp - dst_diff))
return datetime(*args, microsecond=dt.microsecond,
tzinfo=self, fold=fold)
def utcoffset(self, dt):
if self._isdst(dt):
return DSTOFFSET
else:
return STDOFFSET
def dst(self, dt):
if self._isdst(dt):
return DSTDIFF
else:
return ZERO
def tzname(self, dt):
return _time.tzname[self._isdst(dt)]
def _isdst(self, dt):
tt = (dt.year, dt.month, dt.day,
dt.hour, dt.minute, dt.second,
dt.weekday(), 0, 0)
stamp = _time.mktime(tt)
tt = _time.localtime(stamp)
return tt.tm_isdst > 0
Local = LocalTimezone()
# A complete implementation of current DST rules for major US time zones.
def first_sunday_on_or_after(dt):
days_to_go = 6 - dt.weekday()
if days_to_go:
dt += timedelta(days_to_go)
return dt
# US DST Rules
#
# This is a simplified (i.e., wrong for a few cases) set of rules for US
# DST start and end times. For a complete and up-to-date set of DST rules
# and timezone definitions, visit the Olson Database (or try pytz):
# http://www.twinsun.com/tz/tz-link.htm
# http://sourceforge.net/projects/pytz/ (might not be up-to-date)
#
# In the US, since 2007, DST starts at 2am (standard time) on the second
# Sunday in March, which is the first Sunday on or after Mar 8.
DSTSTART_2007 = datetime(1, 3, 8, 2)
# and ends at 2am (DST time) on the first Sunday of Nov.
DSTEND_2007 = datetime(1, 11, 1, 2)
# From 1987 to 2006, DST used to start at 2am (standard time) on the first
# Sunday in April and to end at 2am (DST time) on the last
# Sunday of October, which is the first Sunday on or after Oct 25.
DSTSTART_1987_2006 = datetime(1, 4, 1, 2)
DSTEND_1987_2006 = datetime(1, 10, 25, 2)
# From 1967 to 1986, DST used to start at 2am (standard time) on the last
# Sunday in April (the one on or after April 24) and to end at 2am (DST time)
# on the last Sunday of October, which is the first Sunday
# on or after Oct 25.
DSTSTART_1967_1986 = datetime(1, 4, 24, 2)
DSTEND_1967_1986 = DSTEND_1987_2006
def us_dst_range(year):
# Find start and end times for US DST. For years before 1967, return
# start = end for no DST.
if 2006 < year:
dststart, dstend = DSTSTART_2007, DSTEND_2007
elif 1986 < year < 2007:
dststart, dstend = DSTSTART_1987_2006, DSTEND_1987_2006
elif 1966 < year < 1987:
dststart, dstend = DSTSTART_1967_1986, DSTEND_1967_1986
else:
return (datetime(year, 1, 1), ) * 2
start = first_sunday_on_or_after(dststart.replace(year=year))
end = first_sunday_on_or_after(dstend.replace(year=year))
return start, end
class USTimeZone(tzinfo):
def __init__(self, hours, reprname, stdname, dstname):
self.stdoffset = timedelta(hours=hours)
self.reprname = reprname
self.stdname = stdname
self.dstname = dstname
def __repr__(self):
return self.reprname
def tzname(self, dt):
if self.dst(dt):
return self.dstname
else:
return self.stdname
def utcoffset(self, dt):
return self.stdoffset + self.dst(dt)
def dst(self, dt):
if dt is None or dt.tzinfo is None:
# An exception may be sensible here, in one or both cases.
# It depends on how you want to treat them. The default
# fromutc() implementation (called by the default astimezone()
# implementation) passes a datetime with dt.tzinfo is self.
return ZERO
assert dt.tzinfo is self
start, end = us_dst_range(dt.year)
# Can't compare naive to aware objects, so strip the timezone from
# dt first.
dt = dt.replace(tzinfo=None)
if start + HOUR <= dt < end - HOUR:
# DST is in effect.
return HOUR
if end - HOUR <= dt < end:
# Fold (an ambiguous hour): use dt.fold to disambiguate.
return ZERO if dt.fold else HOUR
if start <= dt < start + HOUR:
# Gap (a non-existent hour): reverse the fold rule.
return HOUR if dt.fold else ZERO
# DST is off.
return ZERO
def fromutc(self, dt):
assert dt.tzinfo is self
start, end = us_dst_range(dt.year)
start = start.replace(tzinfo=self)
end = end.replace(tzinfo=self)
std_time = dt + self.stdoffset
dst_time = std_time + HOUR
if end <= dst_time < end + HOUR:
# Repeated hour
return std_time.replace(fold=1)
if std_time < start or dst_time >= end:
# Standard time
return std_time
if start <= std_time < end - HOUR:
# Daylight saving time
return dst_time
Eastern = USTimeZone(-5, "Eastern", "EST", "EDT")
Central = USTimeZone(-6, "Central", "CST", "CDT")
Mountain = USTimeZone(-7, "Mountain", "MST", "MDT")
Pacific = USTimeZone(-8, "Pacific", "PST", "PDT")
```
Note that there are unavoidable subtleties twice per year in a [`tzinfo`](#datetime.tzinfo "datetime.tzinfo")subclass accounting for both standard and daylight time, at the DST transition points. For concreteness, consider US Eastern (UTC -0500), where EDT begins the minute after 1:59 (EST) on the second Sunday in March, and ends the minute after 1:59 (EDT) on the first Sunday in November:
```
UTC 3:MM 4:MM 5:MM 6:MM 7:MM 8:MM
EST 22:MM 23:MM 0:MM 1:MM 2:MM 3:MM
EDT 23:MM 0:MM 1:MM 2:MM 3:MM 4:MM
start 22:MM 23:MM 0:MM 1:MM 3:MM 4:MM
end 23:MM 0:MM 1:MM 1:MM 2:MM 3:MM
```
When DST starts (the "start" line), the local wall clock leaps from 1:59 to 3:00. A wall time of the form 2:MM doesn't really make sense on that day, so `astimezone(Eastern)` won't deliver a result with `hour == 2` on the day DST begins. For example, at the Spring forward transition of 2016, we get
```
>>> from datetime import datetime, timezone
>>> from tzinfo_examples import HOUR, Eastern
>>> u0 = datetime(2016, 3, 13, 5, tzinfo=timezone.utc)
>>> for i in range(4):
... u = u0 + i*HOUR
... t = u.astimezone(Eastern)
... print(u.time(), 'UTC =', t.time(), t.tzname())
...
05:00:00 UTC = 00:00:00 EST
06:00:00 UTC = 01:00:00 EST
07:00:00 UTC = 03:00:00 EDT
08:00:00 UTC = 04:00:00 EDT
```
When DST ends (the "end" line), there's a potentially worse problem: there's an hour that can't be spelled unambiguously in local wall time: the last hour of daylight time. In Eastern, that's times of the form 5:MM UTC on the day daylight time ends. The local wall clock leaps from 1:59 (daylight time) back to 1:00 (standard time) again. Local times of the form 1:MM are ambiguous. `astimezone()` mimics the local clock's behavior by mapping two adjacent UTC hours into the same local hour then. In the Eastern example, UTC times of the form 5:MM and 6:MM both map to 1:MM when converted to Eastern, but earlier times have the [`fold`](#datetime.datetime.fold "datetime.datetime.fold") attribute set to 0 and the later times have it set to 1. For example, at the Fall back transition of 2016, we get
```
>>> u0 = datetime(2016, 11, 6, 4, tzinfo=timezone.utc)
>>> for i in range(4):
... u = u0 + i*HOUR
... t = u.astimezone(Eastern)
... print(u.time(), 'UTC =', t.time(), t.tzname(), t.fold)
...
04:00:00 UTC = 00:00:00 EDT 0
05:00:00 UTC = 01:00:00 EDT 0
06:00:00 UTC = 01:00:00 EST 1
07:00:00 UTC = 02:00:00 EST 0
```
Note that the [`datetime`](#module-datetime "datetime: Basic date and time types.") instances that differ only by the value of the [`fold`](#datetime.datetime.fold "datetime.datetime.fold") attribute are considered equal in comparisons.
Applications that can't bear wall-time ambiguities should explicitly check the value of the [`fold`](#datetime.datetime.fold "datetime.datetime.fold") attribute or avoid using hybrid [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclasses; there are no ambiguities when using [`timezone`](#datetime.timezone "datetime.timezone"), or any other fixed-offset [`tzinfo`](#datetime.tzinfo "datetime.tzinfo") subclass (such as a class representing only EST (fixed offset -5 hours), or only EDT (fixed offset -4 hours)).
参见
[dateutil.tz](https://dateutil.readthedocs.io/en/stable/tz.html) \[https://dateutil.readthedocs.io/en/stable/tz.html\]The standard library has [`timezone`](#datetime.timezone "datetime.timezone") class for handling arbitrary fixed offsets from UTC and [`timezone.utc`](#datetime.timezone.utc "datetime.timezone.utc") as UTC timezone instance.
*dateutil.tz* library brings the *IANA timezone database* (also known as the Olson database) to Python and its usage is recommended.
[IANA timezone database](https://www.iana.org/time-zones) \[https://www.iana.org/time-zones\]The Time Zone Database (often called tz, tzdata or zoneinfo) contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules.
## [`timezone`](#datetime.timezone "datetime.timezone") Objects
The [`timezone`](#datetime.timezone "datetime.timezone") class is a subclass of [`tzinfo`](#datetime.tzinfo "datetime.tzinfo"), each instance of which represents a timezone defined by a fixed offset from UTC. Note that objects of this class cannot be used to represent timezone information in the locations where different offsets are used in different days of the year or where historical changes have been made to civil time.
*class* `datetime.``timezone`(*offset*, *name=None*)The *offset* argument must be specified as a [`timedelta`](#datetime.timedelta "datetime.timedelta")object representing the difference between the local time and UTC. It must be strictly between `-timedelta(hours=24)` and `timedelta(hours=24)`, otherwise [`ValueError`](exceptions.xhtml#ValueError "ValueError") is raised.
The *name* argument is optional. If specified it must be a string that will be used as the value returned by the [`datetime.tzname()`](#datetime.datetime.tzname "datetime.datetime.tzname") method.
3\.2 新版功能.
在 3.7 版更改: The UTC offset is not restricted to a whole number of minutes.
`timezone.``utcoffset`(*dt*)Return the fixed value specified when the [`timezone`](#datetime.timezone "datetime.timezone") instance is constructed. The *dt* argument is ignored. The return value is a [`timedelta`](#datetime.timedelta "datetime.timedelta") instance equal to the difference between the local time and UTC.
在 3.7 版更改: The UTC offset is not restricted to a whole number of minutes.
`timezone.``tzname`(*dt*)Return the fixed value specified when the [`timezone`](#datetime.timezone "datetime.timezone") instance is constructed. If *name* is not provided in the constructor, the name returned by `tzname(dt)` is generated from the value of the `offset` as follows. If *offset* is `timedelta(0)`, the name is "UTC", otherwise it is a string 'UTC±HH:MM', where ± is the sign of `offset`, HH and MM are two digits of `offset.hours` and `offset.minutes` respectively.
在 3.6 版更改: Name generated from `offset=timedelta(0)` is now plain 'UTC', not 'UTC+00:00'.
`timezone.``dst`(*dt*)Always returns `None`.
`timezone.``fromutc`(*dt*)Return `dt + offset`. The *dt* argument must be an aware [`datetime`](#datetime.datetime "datetime.datetime") instance, with `tzinfo` set to `self`.
Class attributes:
`timezone.``utc`The UTC timezone, `timezone(timedelta(0))`.
## `strftime()` and `strptime()` Behavior
[`date`](#datetime.date "datetime.date"), [`datetime`](#datetime.datetime "datetime.datetime"), and [`time`](#datetime.time "datetime.time") objects all support a `strftime(format)` method, to create a string representing the time under the control of an explicit format string. Broadly speaking, `d.strftime(fmt)`acts like the [`time`](time.xhtml#module-time "time: Time access and conversions.") module's `time.strftime(fmt, d.timetuple())`although not all objects support a `timetuple()` method.
Conversely, the [`datetime.strptime()`](#datetime.datetime.strptime "datetime.datetime.strptime") class method creates a [`datetime`](#datetime.datetime "datetime.datetime") object from a string representing a date and time and a corresponding format string. `datetime.strptime(date_string, format)` is equivalent to `datetime(*(time.strptime(date_string, format)[0:6]))`, except when the format includes sub-second components or timezone offset information, which are supported in `datetime.strptime` but are discarded by `time.strptime`.
For [`time`](#datetime.time "datetime.time") objects, the format codes for year, month, and day should not be used, as time objects have no such values. If they're used anyway, `1900`is substituted for the year, and `1` for the month and day.
For [`date`](#datetime.date "datetime.date") objects, the format codes for hours, minutes, seconds, and microseconds should not be used, as [`date`](#datetime.date "datetime.date") objects have no such values. If they're used anyway, `0` is substituted for them.
The full set of format codes supported varies across platforms, because Python calls the platform C library's `strftime()` function, and platform variations are common. To see the full set of format codes supported on your platform, consult the *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 [`UnicodeError`](exceptions.xhtml#UnicodeError "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 format codes.
指令
意义
示例
注释
`%a`
当地工作日的缩写。
Sun, Mon, ..., Sat (美国);
So, Mo, ..., Sa (德国)
(1)
`%A`
当地工作日的全名。
Sunday, Monday, ..., Saturday (美国);
Sonntag, Montag, ..., Samstag (德国)
(1)
`%w`
以十进制数显示的工作日,其中0表示星期日,6表示星期六。
0, 1, ..., 6
`%d`
补零后,以十进制数显示的月份中的一天。
01, 02, ..., 31
`%b`
当地月份的缩写。
Jan, Feb, ..., Dec (美国);
Jan, Feb, ..., Dez (德国)
(1)
`%B`
当地月份的全名。
January, February, ..., December (美国);
Januar, Februar, ..., Dezember (德国)
(1)
`%m`
补零后,以十进制数显示的月份。
01, 02, ..., 12
`%y`
补零后,以十进制数表示的,不带世纪的年份。
00, 01, ..., 99
`%Y`
十进制数表示的带世纪的年份。
0001, 0002, ..., 2013, 2014, ..., 9998, 9999
(2)
`%H`
Hour (24-hour clock) as a zero-padded decimal number.
00, 01, ..., 23
`%I`
Hour (12-hour clock) as a zero-padded decimal number.
01, 02, ..., 12
`%p`
本地化的 AM 或 PM 。
AM, PM (美国);
am, pm (德国)
(1), (3)
`%M`
补零后,以十进制数显示的分钟。
00, 01, ..., 59
`%S`
补零后,以十进制数显示的秒。
00, 01, ..., 59
(4)
`%f`
Microsecond as a decimal number, zero-padded on the left.
000000, 000001, ..., 999999
(5)
`%z`
UTC offset in the form ±HHMM\[SS\[.ffffff\]\] (empty string if the object is naive).
(empty), +0000, -0400, +1030, +063415, -030712.345216
(6)
`%Z`
Time zone name (empty string if the object is naive).
(empty), UTC, EST, CST
`%j`
Day of the year as a zero-padded decimal number.
001, 002, ..., 366
`%U`
Week number of the year (Sunday as the first day of the week) as a zero padded decimal number. All days in a new year preceding the first Sunday are considered to be in week 0.
00, 01, ..., 53
(7)
`%W`
Week number of the year (Monday as the first day of the week) as a decimal number. All days in a new year preceding the first Monday are considered to be in week 0.
00, 01, ..., 53
(7)
`%c`
本地化的适当日期和时间表示。
Tue Aug 16 21:30:00 1988 (美国);
Di 16 Aug 21:30:00 1988 (德国)
(1)
`%x`
本地化的适当日期表示。
08/16/88 (None);
08/16/1988 (en\_US);
16.08.1988 (de\_DE)
(1)
`%X`
本地化的适当时间表示。
21:30:00 (en\_US);
21:30:00 (de\_DE)
(1)
`%%`
字面的 `'%'` 字符。
%
Several additional directives not required by the C89 standard are included for convenience. These parameters all correspond to ISO 8601 date values. These may not be available on all platforms when used with the `strftime()`method. The ISO 8601 year and ISO 8601 week directives are not interchangeable with the year and week number directives above. Calling `strptime()` with incomplete or ambiguous ISO 8601 directives will raise a [`ValueError`](exceptions.xhtml#ValueError "ValueError").
指令
意义
示例
注释
`%G`
ISO 8601 year with century representing the year that contains the greater part of the ISO week (`%V`).
0001, 0002, ..., 2013, 2014, ..., 9998, 9999
(8)
`%u`
ISO 8601 weekday as a decimal number where 1 is Monday.
1, 2, ..., 7
`%V`
ISO 8601 week as a decimal number with Monday as the first day of the week. Week 01 is the week containing Jan 4.
01, 02, ..., 53
(8)
3\.6 新版功能: `%G`, `%u` and `%V` were added.
注释:
1. 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 [`locale.getlocale()`](locale.xhtml#locale.getlocale "locale.getlocale")to determine the current locale's encoding).
2. The `strptime()` method can parse years in the full \[1, 9999\] range, but years < 1000 must be zero-filled to 4-digit width.
在 3.2 版更改: In previous versions, `strftime()` method was restricted to years >= 1900.
在 3.3 版更改: In version 3.2, `strftime()` method was restricted to years >= 1000.
3. When used with the `strptime()` method, the `%p` directive only affects the output hour field if the `%I` directive is used to parse the hour.
4. Unlike the [`time`](time.xhtml#module-time "time: Time access and conversions.") module, the [`datetime`](#module-datetime "datetime: Basic date and time types.") module does not support leap seconds.
5. When used with the `strptime()` method, the `%f` directive accepts from one to six digits and zero pads on the right. `%f` is an extension to the set of format characters in the C standard (but implemented separately in datetime objects, and therefore always available).
6. For a naive object, the `%z` and `%Z` format codes are replaced by empty strings.
For an aware object:
`%z``utcoffset()` is transformed into a string of the form ±HHMM\[SS\[.ffffff\]\], where HH is a 2-digit string giving the number of UTC offset hours, MM is a 2-digit string giving the number of UTC offset minutes, SS is a 2-digit string giving the number of UTC offset seconds and ffffff is a 6-digit string giving the number of UTC offset microseconds. The ffffff part is omitted when the offset is a whole number of seconds and both the ffffff and the SS part is omitted when the offset is a whole number of minutes. For example, if `utcoffset()` returns `timedelta(hours=-3, minutes=-30)`, `%z` is replaced with the string `'-0330'`.
在 3.7 版更改: The UTC offset is not restricted to a whole number of minutes.
在 3.7 版更改: When the `%z` directive is provided to the `strptime()` method, the UTC offsets can have a colon as a separator between hours, minutes and seconds. For example, `'+01:00:00'` will be parsed as an offset of one hour. In addition, providing `'Z'` is identical to `'+00:00'`.
`%Z`If `tzname()` returns `None`, `%Z` is replaced by an empty string. Otherwise `%Z` is replaced by the returned value, which must be a string.
在 3.2 版更改: When the `%z` directive is provided to the `strptime()` method, an aware [`datetime`](#datetime.datetime "datetime.datetime") object will be produced. The `tzinfo` of the result will be set to a [`timezone`](#datetime.timezone "datetime.timezone") instance.
7. When used with the `strptime()` method, `%U` and `%W` are only used in calculations when the day of the week and the calendar year (`%Y`) are specified.
8. Similar to `%U` and `%W`, `%V` is only used in calculations when the day of the week and the ISO year (`%G`) are specified in a `strptime()` format string. Also note that `%G` and `%Y` are not interchangeable.
脚注
[1](#id1)If, that is, we ignore the effects of Relativity
### 导航
- [索引](../genindex.xhtml "总目录")
- [模块](../py-modindex.xhtml "Python 模块索引") |
- [下一页](calendar.xhtml "calendar --- General calendar-related functions") |
- [上一页](datatypes.xhtml "数据类型") |
- ![](https://box.kancloud.cn/a721fc7ec672275e257bbbfde49a4d4e_16x16.png)
- [Python](https://www.python.org/) »
- zh\_CN 3.7.3 [文档](../index.xhtml) »
- [Python 标准库](index.xhtml) »
- [数据类型](datatypes.xhtml) »
- $('.inline-search').show(0); |
© [版权所有](../copyright.xhtml) 2001-2019, Python Software Foundation.
Python 软件基金会是一个非盈利组织。 [请捐助。](https://www.python.org/psf/donations/)
最后更新于 5月 21, 2019. [发现了问题](../bugs.xhtml)?
使用[Sphinx](http://sphinx.pocoo.org/)1.8.4 创建。
- Python文档内容
- Python 有什么新变化?
- Python 3.7 有什么新变化
- 摘要 - 发布重点
- 新的特性
- 其他语言特性修改
- 新增模块
- 改进的模块
- C API 的改变
- 构建的改变
- 性能优化
- 其他 CPython 实现的改变
- 已弃用的 Python 行为
- 已弃用的 Python 模块、函数和方法
- 已弃用的 C API 函数和类型
- 平台支持的移除
- API 与特性的移除
- 移除的模块
- Windows 专属的改变
- 移植到 Python 3.7
- Python 3.7.1 中的重要变化
- Python 3.7.2 中的重要变化
- Python 3.6 有什么新变化A
- 摘要 - 发布重点
- 新的特性
- 其他语言特性修改
- 新增模块
- 改进的模块
- 性能优化
- Build and C API Changes
- 其他改进
- 弃用
- 移除
- 移植到Python 3.6
- Python 3.6.2 中的重要变化
- Python 3.6.4 中的重要变化
- Python 3.6.5 中的重要变化
- Python 3.6.7 中的重要变化
- Python 3.5 有什么新变化
- 摘要 - 发布重点
- 新的特性
- 其他语言特性修改
- 新增模块
- 改进的模块
- Other module-level changes
- 性能优化
- Build and C API Changes
- 弃用
- 移除
- Porting to Python 3.5
- Notable changes in Python 3.5.4
- What's New In Python 3.4
- 摘要 - 发布重点
- 新的特性
- 新增模块
- 改进的模块
- CPython Implementation Changes
- 弃用
- 移除
- Porting to Python 3.4
- Changed in 3.4.3
- What's New In Python 3.3
- 摘要 - 发布重点
- PEP 405: Virtual Environments
- PEP 420: Implicit Namespace Packages
- PEP 3118: New memoryview implementation and buffer protocol documentation
- PEP 393: Flexible String Representation
- PEP 397: Python Launcher for Windows
- PEP 3151: Reworking the OS and IO exception hierarchy
- PEP 380: Syntax for Delegating to a Subgenerator
- PEP 409: Suppressing exception context
- PEP 414: Explicit Unicode literals
- PEP 3155: Qualified name for classes and functions
- PEP 412: Key-Sharing Dictionary
- PEP 362: Function Signature Object
- PEP 421: Adding sys.implementation
- Using importlib as the Implementation of Import
- 其他语言特性修改
- A Finer-Grained Import Lock
- Builtin functions and types
- 新增模块
- 改进的模块
- 性能优化
- Build and C API Changes
- 弃用
- Porting to Python 3.3
- What's New In Python 3.2
- PEP 384: Defining a Stable ABI
- PEP 389: Argparse Command Line Parsing Module
- PEP 391: Dictionary Based Configuration for Logging
- PEP 3148: The concurrent.futures module
- PEP 3147: PYC Repository Directories
- PEP 3149: ABI Version Tagged .so Files
- PEP 3333: Python Web Server Gateway Interface v1.0.1
- 其他语言特性修改
- New, Improved, and Deprecated Modules
- 多线程
- 性能优化
- Unicode
- Codecs
- 文档
- IDLE
- Code Repository
- Build and C API Changes
- Porting to Python 3.2
- What's New In Python 3.1
- PEP 372: Ordered Dictionaries
- PEP 378: Format Specifier for Thousands Separator
- 其他语言特性修改
- New, Improved, and Deprecated Modules
- 性能优化
- IDLE
- Build and C API Changes
- Porting to Python 3.1
- What's New In Python 3.0
- Common Stumbling Blocks
- Overview Of Syntax Changes
- Changes Already Present In Python 2.6
- Library Changes
- PEP 3101: A New Approach To String Formatting
- Changes To Exceptions
- Miscellaneous Other Changes
- Build and C API Changes
- 性能
- Porting To Python 3.0
- What's New in Python 2.7
- The Future for Python 2.x
- Changes to the Handling of Deprecation Warnings
- Python 3.1 Features
- PEP 372: Adding an Ordered Dictionary to collections
- PEP 378: Format Specifier for Thousands Separator
- PEP 389: The argparse Module for Parsing Command Lines
- PEP 391: Dictionary-Based Configuration For Logging
- PEP 3106: Dictionary Views
- PEP 3137: The memoryview Object
- 其他语言特性修改
- New and Improved Modules
- Build and C API Changes
- Other Changes and Fixes
- Porting to Python 2.7
- New Features Added to Python 2.7 Maintenance Releases
- Acknowledgements
- Python 2.6 有什么新变化
- Python 3.0
- Changes to the Development Process
- PEP 343: The 'with' statement
- PEP 366: Explicit Relative Imports From a Main Module
- PEP 370: Per-user site-packages Directory
- PEP 371: The multiprocessing Package
- PEP 3101: Advanced String Formatting
- PEP 3105: print As a Function
- PEP 3110: Exception-Handling Changes
- PEP 3112: Byte Literals
- PEP 3116: New I/O Library
- PEP 3118: Revised Buffer Protocol
- PEP 3119: Abstract Base Classes
- PEP 3127: Integer Literal Support and Syntax
- PEP 3129: Class Decorators
- PEP 3141: A Type Hierarchy for Numbers
- 其他语言特性修改
- New and Improved Modules
- Deprecations and Removals
- Build and C API Changes
- Porting to Python 2.6
- Acknowledgements
- What's New in Python 2.5
- PEP 308: Conditional Expressions
- PEP 309: Partial Function Application
- PEP 314: Metadata for Python Software Packages v1.1
- PEP 328: Absolute and Relative Imports
- PEP 338: Executing Modules as Scripts
- PEP 341: Unified try/except/finally
- PEP 342: New Generator Features
- PEP 343: The 'with' statement
- PEP 352: Exceptions as New-Style Classes
- PEP 353: Using ssize_t as the index type
- PEP 357: The 'index' method
- 其他语言特性修改
- New, Improved, and Removed Modules
- Build and C API Changes
- Porting to Python 2.5
- Acknowledgements
- What's New in Python 2.4
- PEP 218: Built-In Set Objects
- PEP 237: Unifying Long Integers and Integers
- PEP 289: Generator Expressions
- PEP 292: Simpler String Substitutions
- PEP 318: Decorators for Functions and Methods
- PEP 322: Reverse Iteration
- PEP 324: New subprocess Module
- PEP 327: Decimal Data Type
- PEP 328: Multi-line Imports
- PEP 331: Locale-Independent Float/String Conversions
- 其他语言特性修改
- New, Improved, and Deprecated Modules
- Build and C API Changes
- Porting to Python 2.4
- Acknowledgements
- What's New in Python 2.3
- PEP 218: A Standard Set Datatype
- PEP 255: Simple Generators
- PEP 263: Source Code Encodings
- PEP 273: Importing Modules from ZIP Archives
- PEP 277: Unicode file name support for Windows NT
- PEP 278: Universal Newline Support
- PEP 279: enumerate()
- PEP 282: The logging Package
- PEP 285: A Boolean Type
- PEP 293: Codec Error Handling Callbacks
- PEP 301: Package Index and Metadata for Distutils
- PEP 302: New Import Hooks
- PEP 305: Comma-separated Files
- PEP 307: Pickle Enhancements
- Extended Slices
- 其他语言特性修改
- New, Improved, and Deprecated Modules
- Pymalloc: A Specialized Object Allocator
- Build and C API Changes
- Other Changes and Fixes
- Porting to Python 2.3
- Acknowledgements
- What's New in Python 2.2
- 概述
- PEPs 252 and 253: Type and Class Changes
- PEP 234: Iterators
- PEP 255: Simple Generators
- PEP 237: Unifying Long Integers and Integers
- PEP 238: Changing the Division Operator
- Unicode Changes
- PEP 227: Nested Scopes
- New and Improved Modules
- Interpreter Changes and Fixes
- Other Changes and Fixes
- Acknowledgements
- What's New in Python 2.1
- 概述
- PEP 227: Nested Scopes
- PEP 236: future Directives
- PEP 207: Rich Comparisons
- PEP 230: Warning Framework
- PEP 229: New Build System
- PEP 205: Weak References
- PEP 232: Function Attributes
- PEP 235: Importing Modules on Case-Insensitive Platforms
- PEP 217: Interactive Display Hook
- PEP 208: New Coercion Model
- PEP 241: Metadata in Python Packages
- New and Improved Modules
- Other Changes and Fixes
- Acknowledgements
- What's New in Python 2.0
- 概述
- What About Python 1.6?
- New Development Process
- Unicode
- 列表推导式
- Augmented Assignment
- 字符串的方法
- Garbage Collection of Cycles
- Other Core Changes
- Porting to 2.0
- Extending/Embedding Changes
- Distutils: Making Modules Easy to Install
- XML Modules
- Module changes
- New modules
- IDLE Improvements
- Deleted and Deprecated Modules
- Acknowledgements
- 更新日志
- Python 下一版
- Python 3.7.3 最终版
- Python 3.7.3 发布候选版 1
- Python 3.7.2 最终版
- Python 3.7.2 发布候选版 1
- Python 3.7.1 最终版
- Python 3.7.1 RC 2版本
- Python 3.7.1 发布候选版 1
- Python 3.7.0 正式版
- Python 3.7.0 release candidate 1
- Python 3.7.0 beta 5
- Python 3.7.0 beta 4
- Python 3.7.0 beta 3
- Python 3.7.0 beta 2
- Python 3.7.0 beta 1
- Python 3.7.0 alpha 4
- Python 3.7.0 alpha 3
- Python 3.7.0 alpha 2
- Python 3.7.0 alpha 1
- Python 3.6.6 final
- Python 3.6.6 RC 1
- Python 3.6.5 final
- Python 3.6.5 release candidate 1
- Python 3.6.4 final
- Python 3.6.4 release candidate 1
- Python 3.6.3 final
- Python 3.6.3 release candidate 1
- Python 3.6.2 final
- Python 3.6.2 release candidate 2
- Python 3.6.2 release candidate 1
- Python 3.6.1 final
- Python 3.6.1 release candidate 1
- Python 3.6.0 final
- Python 3.6.0 release candidate 2
- Python 3.6.0 release candidate 1
- Python 3.6.0 beta 4
- Python 3.6.0 beta 3
- Python 3.6.0 beta 2
- Python 3.6.0 beta 1
- Python 3.6.0 alpha 4
- Python 3.6.0 alpha 3
- Python 3.6.0 alpha 2
- Python 3.6.0 alpha 1
- Python 3.5.5 final
- Python 3.5.5 release candidate 1
- Python 3.5.4 final
- Python 3.5.4 release candidate 1
- Python 3.5.3 final
- Python 3.5.3 release candidate 1
- Python 3.5.2 final
- Python 3.5.2 release candidate 1
- Python 3.5.1 final
- Python 3.5.1 release candidate 1
- Python 3.5.0 final
- Python 3.5.0 release candidate 4
- Python 3.5.0 release candidate 3
- Python 3.5.0 release candidate 2
- Python 3.5.0 release candidate 1
- Python 3.5.0 beta 4
- Python 3.5.0 beta 3
- Python 3.5.0 beta 2
- Python 3.5.0 beta 1
- Python 3.5.0 alpha 4
- Python 3.5.0 alpha 3
- Python 3.5.0 alpha 2
- Python 3.5.0 alpha 1
- Python 教程
- 课前甜点
- 使用 Python 解释器
- 调用解释器
- 解释器的运行环境
- Python 的非正式介绍
- Python 作为计算器使用
- 走向编程的第一步
- 其他流程控制工具
- if 语句
- for 语句
- range() 函数
- break 和 continue 语句,以及循环中的 else 子句
- pass 语句
- 定义函数
- 函数定义的更多形式
- 小插曲:编码风格
- 数据结构
- 列表的更多特性
- del 语句
- 元组和序列
- 集合
- 字典
- 循环的技巧
- 深入条件控制
- 序列和其它类型的比较
- 模块
- 有关模块的更多信息
- 标准模块
- dir() 函数
- 包
- 输入输出
- 更漂亮的输出格式
- 读写文件
- 错误和异常
- 语法错误
- 异常
- 处理异常
- 抛出异常
- 用户自定义异常
- 定义清理操作
- 预定义的清理操作
- 类
- 名称和对象
- Python 作用域和命名空间
- 初探类
- 补充说明
- 继承
- 私有变量
- 杂项说明
- 迭代器
- 生成器
- 生成器表达式
- 标准库简介
- 操作系统接口
- 文件通配符
- 命令行参数
- 错误输出重定向和程序终止
- 字符串模式匹配
- 数学
- 互联网访问
- 日期和时间
- 数据压缩
- 性能测量
- 质量控制
- 自带电池
- 标准库简介 —— 第二部分
- 格式化输出
- 模板
- 使用二进制数据记录格式
- 多线程
- 日志
- 弱引用
- 用于操作列表的工具
- 十进制浮点运算
- 虚拟环境和包
- 概述
- 创建虚拟环境
- 使用pip管理包
- 接下来?
- 交互式编辑和编辑历史
- Tab 补全和编辑历史
- 默认交互式解释器的替代品
- 浮点算术:争议和限制
- 表示性错误
- 附录
- 交互模式
- 安装和使用 Python
- 命令行与环境
- 命令行
- 环境变量
- 在Unix平台中使用Python
- 获取最新版本的Python
- 构建Python
- 与Python相关的路径和文件
- 杂项
- 编辑器和集成开发环境
- 在Windows上使用 Python
- 完整安装程序
- Microsoft Store包
- nuget.org 安装包
- 可嵌入的包
- 替代捆绑包
- 配置Python
- 适用于Windows的Python启动器
- 查找模块
- 附加模块
- 在Windows上编译Python
- 其他平台
- 在苹果系统上使用 Python
- 获取和安装 MacPython
- IDE
- 安装额外的 Python 包
- Mac 上的图形界面编程
- 在 Mac 上分发 Python 应用程序
- 其他资源
- Python 语言参考
- 概述
- 其他实现
- 标注
- 词法分析
- 行结构
- 其他形符
- 标识符和关键字
- 字面值
- 运算符
- 分隔符
- 数据模型
- 对象、值与类型
- 标准类型层级结构
- 特殊方法名称
- 协程
- 执行模型
- 程序的结构
- 命名与绑定
- 异常
- 导入系统
- importlib
- 包
- 搜索
- 加载
- 基于路径的查找器
- 替换标准导入系统
- Package Relative Imports
- 有关 main 的特殊事项
- 开放问题项
- 参考文献
- 表达式
- 算术转换
- 原子
- 原型
- await 表达式
- 幂运算符
- 一元算术和位运算
- 二元算术运算符
- 移位运算
- 二元位运算
- 比较运算
- 布尔运算
- 条件表达式
- lambda 表达式
- 表达式列表
- 求值顺序
- 运算符优先级
- 简单语句
- 表达式语句
- 赋值语句
- assert 语句
- pass 语句
- del 语句
- return 语句
- yield 语句
- raise 语句
- break 语句
- continue 语句
- import 语句
- global 语句
- nonlocal 语句
- 复合语句
- if 语句
- while 语句
- for 语句
- try 语句
- with 语句
- 函数定义
- 类定义
- 协程
- 最高层级组件
- 完整的 Python 程序
- 文件输入
- 交互式输入
- 表达式输入
- 完整的语法规范
- Python 标准库
- 概述
- 可用性注释
- 内置函数
- 内置常量
- 由 site 模块添加的常量
- 内置类型
- 逻辑值检测
- 布尔运算 — and, or, not
- 比较
- 数字类型 — int, float, complex
- 迭代器类型
- 序列类型 — list, tuple, range
- 文本序列类型 — str
- 二进制序列类型 — bytes, bytearray, memoryview
- 集合类型 — set, frozenset
- 映射类型 — dict
- 上下文管理器类型
- 其他内置类型
- 特殊属性
- 内置异常
- 基类
- 具体异常
- 警告
- 异常层次结构
- 文本处理服务
- string — 常见的字符串操作
- re — 正则表达式操作
- 模块 difflib 是一个计算差异的助手
- textwrap — Text wrapping and filling
- unicodedata — Unicode 数据库
- stringprep — Internet String Preparation
- readline — GNU readline interface
- rlcompleter — GNU readline的完成函数
- 二进制数据服务
- struct — Interpret bytes as packed binary data
- codecs — Codec registry and base classes
- 数据类型
- datetime — 基础日期/时间数据类型
- calendar — General calendar-related functions
- collections — 容器数据类型
- collections.abc — 容器的抽象基类
- heapq — 堆队列算法
- bisect — Array bisection algorithm
- array — Efficient arrays of numeric values
- weakref — 弱引用
- types — Dynamic type creation and names for built-in types
- copy — 浅层 (shallow) 和深层 (deep) 复制操作
- pprint — 数据美化输出
- reprlib — Alternate repr() implementation
- enum — Support for enumerations
- 数字和数学模块
- numbers — 数字的抽象基类
- math — 数学函数
- cmath — Mathematical functions for complex numbers
- decimal — 十进制定点和浮点运算
- fractions — 分数
- random — 生成伪随机数
- statistics — Mathematical statistics functions
- 函数式编程模块
- itertools — 为高效循环而创建迭代器的函数
- functools — 高阶函数和可调用对象上的操作
- operator — 标准运算符替代函数
- 文件和目录访问
- pathlib — 面向对象的文件系统路径
- os.path — 常见路径操作
- fileinput — Iterate over lines from multiple input streams
- stat — Interpreting stat() results
- filecmp — File and Directory Comparisons
- tempfile — Generate temporary files and directories
- glob — Unix style pathname pattern expansion
- fnmatch — Unix filename pattern matching
- linecache — Random access to text lines
- shutil — High-level file operations
- macpath — Mac OS 9 路径操作函数
- 数据持久化
- pickle —— Python 对象序列化
- copyreg — Register pickle support functions
- shelve — Python object persistence
- marshal — Internal Python object serialization
- dbm — Interfaces to Unix “databases”
- sqlite3 — SQLite 数据库 DB-API 2.0 接口模块
- 数据压缩和存档
- zlib — 与 gzip 兼容的压缩
- gzip — 对 gzip 格式的支持
- bz2 — 对 bzip2 压缩算法的支持
- lzma — 用 LZMA 算法压缩
- zipfile — 在 ZIP 归档中工作
- tarfile — Read and write tar archive files
- 文件格式
- csv — CSV 文件读写
- configparser — Configuration file parser
- netrc — netrc file processing
- xdrlib — Encode and decode XDR data
- plistlib — Generate and parse Mac OS X .plist files
- 加密服务
- hashlib — 安全哈希与消息摘要
- hmac — 基于密钥的消息验证
- secrets — Generate secure random numbers for managing secrets
- 通用操作系统服务
- os — 操作系统接口模块
- io — 处理流的核心工具
- time — 时间的访问和转换
- argparse — 命令行选项、参数和子命令解析器
- getopt — C-style parser for command line options
- 模块 logging — Python 的日志记录工具
- logging.config — 日志记录配置
- logging.handlers — Logging handlers
- getpass — 便携式密码输入工具
- curses — 终端字符单元显示的处理
- curses.textpad — Text input widget for curses programs
- curses.ascii — Utilities for ASCII characters
- curses.panel — A panel stack extension for curses
- platform — Access to underlying platform's identifying data
- errno — Standard errno system symbols
- ctypes — Python 的外部函数库
- 并发执行
- threading — 基于线程的并行
- multiprocessing — 基于进程的并行
- concurrent 包
- concurrent.futures — 启动并行任务
- subprocess — 子进程管理
- sched — 事件调度器
- queue — 一个同步的队列类
- _thread — 底层多线程 API
- _dummy_thread — _thread 的替代模块
- dummy_threading — 可直接替代 threading 模块。
- contextvars — Context Variables
- Context Variables
- Manual Context Management
- asyncio support
- 网络和进程间通信
- asyncio — 异步 I/O
- socket — 底层网络接口
- ssl — TLS/SSL wrapper for socket objects
- select — Waiting for I/O completion
- selectors — 高级 I/O 复用库
- asyncore — 异步socket处理器
- asynchat — 异步 socket 指令/响应 处理器
- signal — Set handlers for asynchronous events
- mmap — Memory-mapped file support
- 互联网数据处理
- email — 电子邮件与 MIME 处理包
- json — JSON 编码和解码器
- mailcap — Mailcap file handling
- mailbox — Manipulate mailboxes in various formats
- mimetypes — Map filenames to MIME types
- base64 — Base16, Base32, Base64, Base85 数据编码
- binhex — 对binhex4文件进行编码和解码
- binascii — 二进制和 ASCII 码互转
- quopri — Encode and decode MIME quoted-printable data
- uu — Encode and decode uuencode files
- 结构化标记处理工具
- html — 超文本标记语言支持
- html.parser — 简单的 HTML 和 XHTML 解析器
- html.entities — HTML 一般实体的定义
- XML处理模块
- xml.etree.ElementTree — The ElementTree XML API
- xml.dom — The Document Object Model API
- xml.dom.minidom — Minimal DOM implementation
- xml.dom.pulldom — Support for building partial DOM trees
- xml.sax — Support for SAX2 parsers
- xml.sax.handler — Base classes for SAX handlers
- xml.sax.saxutils — SAX Utilities
- xml.sax.xmlreader — Interface for XML parsers
- xml.parsers.expat — Fast XML parsing using Expat
- 互联网协议和支持
- webbrowser — 方便的Web浏览器控制器
- cgi — Common Gateway Interface support
- cgitb — Traceback manager for CGI scripts
- wsgiref — WSGI Utilities and Reference Implementation
- urllib — URL 处理模块
- urllib.request — 用于打开 URL 的可扩展库
- urllib.response — Response classes used by urllib
- urllib.parse — Parse URLs into components
- urllib.error — Exception classes raised by urllib.request
- urllib.robotparser — Parser for robots.txt
- http — HTTP 模块
- http.client — HTTP协议客户端
- ftplib — FTP protocol client
- poplib — POP3 protocol client
- imaplib — IMAP4 protocol client
- nntplib — NNTP protocol client
- smtplib —SMTP协议客户端
- smtpd — SMTP Server
- telnetlib — Telnet client
- uuid — UUID objects according to RFC 4122
- socketserver — A framework for network servers
- http.server — HTTP 服务器
- http.cookies — HTTP state management
- http.cookiejar — Cookie handling for HTTP clients
- xmlrpc — XMLRPC 服务端与客户端模块
- xmlrpc.client — XML-RPC client access
- xmlrpc.server — Basic XML-RPC servers
- ipaddress — IPv4/IPv6 manipulation library
- 多媒体服务
- audioop — Manipulate raw audio data
- aifc — Read and write AIFF and AIFC files
- sunau — 读写 Sun AU 文件
- wave — 读写WAV格式文件
- chunk — Read IFF chunked data
- colorsys — Conversions between color systems
- imghdr — 推测图像类型
- sndhdr — 推测声音文件的类型
- ossaudiodev — Access to OSS-compatible audio devices
- 国际化
- gettext — 多语种国际化服务
- locale — 国际化服务
- 程序框架
- turtle — 海龟绘图
- cmd — 支持面向行的命令解释器
- shlex — Simple lexical analysis
- Tk图形用户界面(GUI)
- tkinter — Tcl/Tk的Python接口
- tkinter.ttk — Tk themed widgets
- tkinter.tix — Extension widgets for Tk
- tkinter.scrolledtext — 滚动文字控件
- IDLE
- 其他图形用户界面(GUI)包
- 开发工具
- typing — 类型标注支持
- pydoc — Documentation generator and online help system
- doctest — Test interactive Python examples
- unittest — 单元测试框架
- unittest.mock — mock object library
- unittest.mock 上手指南
- 2to3 - 自动将 Python 2 代码转为 Python 3 代码
- test — Regression tests package for Python
- test.support — Utilities for the Python test suite
- test.support.script_helper — Utilities for the Python execution tests
- 调试和分析
- bdb — Debugger framework
- faulthandler — Dump the Python traceback
- pdb — The Python Debugger
- The Python Profilers
- timeit — 测量小代码片段的执行时间
- trace — Trace or track Python statement execution
- tracemalloc — Trace memory allocations
- 软件打包和分发
- distutils — 构建和安装 Python 模块
- ensurepip — Bootstrapping the pip installer
- venv — 创建虚拟环境
- zipapp — Manage executable Python zip archives
- Python运行时服务
- sys — 系统相关的参数和函数
- sysconfig — Provide access to Python's configuration information
- builtins — 内建对象
- main — 顶层脚本环境
- warnings — Warning control
- dataclasses — 数据类
- contextlib — Utilities for with-statement contexts
- abc — 抽象基类
- atexit — 退出处理器
- traceback — Print or retrieve a stack traceback
- future — Future 语句定义
- gc — 垃圾回收器接口
- inspect — 检查对象
- site — Site-specific configuration hook
- 自定义 Python 解释器
- code — Interpreter base classes
- codeop — Compile Python code
- 导入模块
- zipimport — Import modules from Zip archives
- pkgutil — Package extension utility
- modulefinder — 查找脚本使用的模块
- runpy — Locating and executing Python modules
- importlib — The implementation of import
- Python 语言服务
- parser — Access Python parse trees
- ast — 抽象语法树
- symtable — Access to the compiler's symbol tables
- symbol — 与 Python 解析树一起使用的常量
- token — 与Python解析树一起使用的常量
- keyword — 检验Python关键字
- tokenize — Tokenizer for Python source
- tabnanny — 模糊缩进检测
- pyclbr — Python class browser support
- py_compile — Compile Python source files
- compileall — Byte-compile Python libraries
- dis — Python 字节码反汇编器
- pickletools — Tools for pickle developers
- 杂项服务
- formatter — Generic output formatting
- Windows系统相关模块
- msilib — Read and write Microsoft Installer files
- msvcrt — Useful routines from the MS VC++ runtime
- winreg — Windows 注册表访问
- winsound — Sound-playing interface for Windows
- Unix 专有服务
- posix — The most common POSIX system calls
- pwd — 用户密码数据库
- spwd — The shadow password database
- grp — The group database
- crypt — Function to check Unix passwords
- termios — POSIX style tty control
- tty — 终端控制功能
- pty — Pseudo-terminal utilities
- fcntl — The fcntl and ioctl system calls
- pipes — Interface to shell pipelines
- resource — Resource usage information
- nis — Interface to Sun's NIS (Yellow Pages)
- Unix syslog 库例程
- 被取代的模块
- optparse — Parser for command line options
- imp — Access the import internals
- 未创建文档的模块
- 平台特定模块
- 扩展和嵌入 Python 解释器
- 推荐的第三方工具
- 不使用第三方工具创建扩展
- 使用 C 或 C++ 扩展 Python
- 自定义扩展类型:教程
- 定义扩展类型:已分类主题
- 构建C/C++扩展
- 在Windows平台编译C和C++扩展
- 在更大的应用程序中嵌入 CPython 运行时
- Embedding Python in Another Application
- Python/C API 参考手册
- 概述
- 代码标准
- 包含文件
- 有用的宏
- 对象、类型和引用计数
- 异常
- 嵌入Python
- 调试构建
- 稳定的应用程序二进制接口
- The Very High Level Layer
- Reference Counting
- 异常处理
- Printing and clearing
- 抛出异常
- Issuing warnings
- Querying the error indicator
- Signal Handling
- Exception Classes
- Exception Objects
- Unicode Exception Objects
- Recursion Control
- 标准异常
- 标准警告类别
- 工具
- 操作系统实用程序
- 系统功能
- 过程控制
- 导入模块
- Data marshalling support
- 语句解释及变量编译
- 字符串转换与格式化
- 反射
- 编解码器注册与支持功能
- 抽象对象层
- Object Protocol
- 数字协议
- Sequence Protocol
- Mapping Protocol
- 迭代器协议
- 缓冲协议
- Old Buffer Protocol
- 具体的对象层
- 基本对象
- 数值对象
- 序列对象
- 容器对象
- 函数对象
- 其他对象
- Initialization, Finalization, and Threads
- 在Python初始化之前
- 全局配置变量
- Initializing and finalizing the interpreter
- Process-wide parameters
- Thread State and the Global Interpreter Lock
- Sub-interpreter support
- Asynchronous Notifications
- Profiling and Tracing
- Advanced Debugger Support
- Thread Local Storage Support
- 内存管理
- 概述
- 原始内存接口
- Memory Interface
- 对象分配器
- 默认内存分配器
- Customize Memory Allocators
- The pymalloc allocator
- tracemalloc C API
- 示例
- 对象实现支持
- 在堆中分配对象
- Common Object Structures
- Type 对象
- Number Object Structures
- Mapping Object Structures
- Sequence Object Structures
- Buffer Object Structures
- Async Object Structures
- 使对象类型支持循环垃圾回收
- API 和 ABI 版本管理
- 分发 Python 模块
- 关键术语
- 开源许可与协作
- 安装工具
- 阅读指南
- 我该如何...?
- ...为我的项目选择一个名字?
- ...创建和分发二进制扩展?
- 安装 Python 模块
- 关键术语
- 基本使用
- 我应如何 ...?
- ... 在 Python 3.4 之前的 Python 版本中安装 pip ?
- ... 只为当前用户安装软件包?
- ... 安装科学计算类 Python 软件包?
- ... 使用并行安装的多个 Python 版本?
- 常见的安装问题
- 在 Linux 的系统 Python 版本上安装
- 未安装 pip
- 安装二进制编译扩展
- Python 常用指引
- 将 Python 2 代码迁移到 Python 3
- 简要说明
- 详情
- 将扩展模块移植到 Python 3
- 条件编译
- 对象API的更改
- 模块初始化和状态
- CObject 替换为 Capsule
- 其他选项
- Curses Programming with Python
- What is curses?
- Starting and ending a curses application
- Windows and Pads
- Displaying Text
- User Input
- For More Information
- 实现描述器
- 摘要
- 定义和简介
- 描述器协议
- 发起调用描述符
- 描述符示例
- Properties
- 函数和方法
- Static Methods and Class Methods
- 函数式编程指引
- 概述
- 迭代器
- 生成器表达式和列表推导式
- 生成器
- 内置函数
- itertools 模块
- The functools module
- Small functions and the lambda expression
- Revision History and Acknowledgements
- 引用文献
- 日志 HOWTO
- 日志基础教程
- 进阶日志教程
- 日志级别
- 有用的处理程序
- 记录日志中引发的异常
- 使用任意对象作为消息
- 优化
- 日志操作手册
- 在多个模块中使用日志
- 在多线程中使用日志
- 使用多个日志处理器和多种格式化
- 在多个地方记录日志
- 日志服务器配置示例
- 处理日志处理器的阻塞
- Sending and receiving logging events across a network
- Adding contextual information to your logging output
- Logging to a single file from multiple processes
- Using file rotation
- Use of alternative formatting styles
- Customizing LogRecord
- Subclassing QueueHandler - a ZeroMQ example
- Subclassing QueueListener - a ZeroMQ example
- An example dictionary-based configuration
- Using a rotator and namer to customize log rotation processing
- A more elaborate multiprocessing example
- Inserting a BOM into messages sent to a SysLogHandler
- Implementing structured logging
- Customizing handlers with dictConfig()
- Using particular formatting styles throughout your application
- Configuring filters with dictConfig()
- Customized exception formatting
- Speaking logging messages
- Buffering logging messages and outputting them conditionally
- Formatting times using UTC (GMT) via configuration
- Using a context manager for selective logging
- 正则表达式HOWTO
- 概述
- 简单模式
- 使用正则表达式
- 更多模式能力
- 修改字符串
- 常见问题
- 反馈
- 套接字编程指南
- 套接字
- 创建套接字
- 使用一个套接字
- 断开连接
- 非阻塞的套接字
- 排序指南
- 基本排序
- 关键函数
- Operator 模块函数
- 升序和降序
- 排序稳定性和排序复杂度
- 使用装饰-排序-去装饰的旧方法
- 使用 cmp 参数的旧方法
- 其它
- Unicode 指南
- Unicode 概述
- Python's Unicode Support
- Reading and Writing Unicode Data
- Acknowledgements
- 如何使用urllib包获取网络资源
- 概述
- Fetching URLs
- 处理异常
- info and geturl
- Openers and Handlers
- Basic Authentication
- Proxies
- Sockets and Layers
- 脚注
- Argparse 教程
- 概念
- 基础
- 位置参数介绍
- Introducing Optional arguments
- Combining Positional and Optional arguments
- Getting a little more advanced
- Conclusion
- ipaddress模块介绍
- 创建 Address/Network/Interface 对象
- 审查 Address/Network/Interface 对象
- Network 作为 Address 列表
- 比较
- 将IP地址与其他模块一起使用
- 实例创建失败时获取更多详细信息
- Argument Clinic How-To
- The Goals Of Argument Clinic
- Basic Concepts And Usage
- Converting Your First Function
- Advanced Topics
- 使用 DTrace 和 SystemTap 检测CPython
- Enabling the static markers
- Static DTrace probes
- Static SystemTap markers
- Available static markers
- SystemTap Tapsets
- 示例
- Python 常见问题
- Python常见问题
- 一般信息
- 现实世界中的 Python
- 编程常见问题
- 一般问题
- 核心语言
- 数字和字符串
- 性能
- 序列(元组/列表)
- 对象
- 模块
- 设计和历史常见问题
- 为什么Python使用缩进来分组语句?
- 为什么简单的算术运算得到奇怪的结果?
- 为什么浮点计算不准确?
- 为什么Python字符串是不可变的?
- 为什么必须在方法定义和调用中显式使用“self”?
- 为什么不能在表达式中赋值?
- 为什么Python对某些功能(例如list.index())使用方法来实现,而其他功能(例如len(List))使用函数实现?
- 为什么 join()是一个字符串方法而不是列表或元组方法?
- 异常有多快?
- 为什么Python中没有switch或case语句?
- 难道不能在解释器中模拟线程,而非得依赖特定于操作系统的线程实现吗?
- 为什么lambda表达式不能包含语句?
- 可以将Python编译为机器代码,C或其他语言吗?
- Python如何管理内存?
- 为什么CPython不使用更传统的垃圾回收方案?
- CPython退出时为什么不释放所有内存?
- 为什么有单独的元组和列表数据类型?
- 列表是如何在CPython中实现的?
- 字典是如何在CPython中实现的?
- 为什么字典key必须是不可变的?
- 为什么 list.sort() 没有返回排序列表?
- 如何在Python中指定和实施接口规范?
- 为什么没有goto?
- 为什么原始字符串(r-strings)不能以反斜杠结尾?
- 为什么Python没有属性赋值的“with”语句?
- 为什么 if/while/def/class语句需要冒号?
- 为什么Python在列表和元组的末尾允许使用逗号?
- 代码库和插件 FAQ
- 通用的代码库问题
- 通用任务
- 线程相关
- 输入输出
- 网络 / Internet 编程
- 数据库
- 数学和数字
- 扩展/嵌入常见问题
- 可以使用C语言中创建自己的函数吗?
- 可以使用C++语言中创建自己的函数吗?
- C很难写,有没有其他选择?
- 如何从C执行任意Python语句?
- 如何从C中评估任意Python表达式?
- 如何从Python对象中提取C的值?
- 如何使用Py_BuildValue()创建任意长度的元组?
- 如何从C调用对象的方法?
- 如何捕获PyErr_Print()(或打印到stdout / stderr的任何内容)的输出?
- 如何从C访问用Python编写的模块?
- 如何从Python接口到C ++对象?
- 我使用Setup文件添加了一个模块,为什么make失败了?
- 如何调试扩展?
- 我想在Linux系统上编译一个Python模块,但是缺少一些文件。为什么?
- 如何区分“输入不完整”和“输入无效”?
- 如何找到未定义的g++符号__builtin_new或__pure_virtual?
- 能否创建一个对象类,其中部分方法在C中实现,而其他方法在Python中实现(例如通过继承)?
- Python在Windows上的常见问题
- 我怎样在Windows下运行一个Python程序?
- 我怎么让 Python 脚本可执行?
- 为什么有时候 Python 程序会启动缓慢?
- 我怎样使用Python脚本制作可执行文件?
- *.pyd 文件和DLL文件相同吗?
- 我怎样将Python嵌入一个Windows程序?
- 如何让编辑器不要在我的 Python 源代码中插入 tab ?
- 如何在不阻塞的情况下检查按键?
- 图形用户界面(GUI)常见问题
- 图形界面常见问题
- Python 是否有平台无关的图形界面工具包?
- 有哪些Python的GUI工具是某个平台专用的?
- 有关Tkinter的问题
- “为什么我的电脑上安装了 Python ?”
- 什么是Python?
- 为什么我的电脑上安装了 Python ?
- 我能删除 Python 吗?
- 术语对照表
- 文档说明
- Python 文档贡献者
- 解决 Bug
- 文档错误
- 使用 Python 的错误追踪系统
- 开始为 Python 贡献您的知识
- 版权
- 历史和许可证
- 软件历史
- 访问Python或以其他方式使用Python的条款和条件
- Python 3.7.3 的 PSF 许可协议
- Python 2.0 的 BeOpen.com 许可协议
- Python 1.6.1 的 CNRI 许可协议
- Python 0.9.0 至 1.2 的 CWI 许可协议
- 集成软件的许可和认可
- Mersenne Twister
- 套接字
- Asynchronous socket services
- Cookie management
- Execution tracing
- UUencode and UUdecode functions
- XML Remote Procedure Calls
- test_epoll
- Select kqueue
- SipHash24
- strtod and dtoa
- OpenSSL
- expat
- libffi
- zlib
- cfuhash
- libmpdec