datetime --- 日期與時間的基本型別¶
原始碼:Lib/datetime.py
datetime 模組提供操作日期與時間的類別。
While date and time arithmetic is supported, the focus of the implementation ison efficient attribute extraction for output formatting and manipulation.
小訣竅
也參考
calendar模組與日曆相關的一般函式。
time模組Time access and conversions.
zoneinfo模組Concrete time zones representing the IANA time zone database.
- Packagedateutil
帶有時區與剖析擴充支援的第三方函式庫。
- DateType 套件
Third-party library that introduces distinct static types to e.g. allowstatic type checkersto differentiate between naive and aware datetimes.
Aware and Naive Objects¶
Date and time objects may be categorized as "aware" or "naive" depending onwhether or not they include time zone information.
With sufficient knowledge of applicable algorithmic and political timeadjustments, such as time zone and daylight saving time information,anaware object can locate itself relative to other aware objects.An aware object represents a specific moment in time that is not open tointerpretation.[1]
Anaive object does not contain enough information to unambiguously locateitself relative to other date/time objects. Whether a naive object representsCoordinated Universal Time (UTC), local time, or time in some other time zone ispurely up to the program, just like it is up to the program whether aparticular number represents metres, miles, or mass. Naive objects are easy tounderstand and to work with, at the cost of ignoring some aspects of reality.
For applications requiring aware objects,datetime andtimeobjects have an optional time zone information attribute,tzinfo, thatcan be set to an instance of a subclass of the abstracttzinfo class.Thesetzinfo objects capture information about the offset from UTCtime, the time zone name, and whether daylight saving time is in effect.
Only one concretetzinfo class, thetimezone class, issupplied by thedatetime module. Thetimezone class canrepresent simple time zones with fixed offsets from UTC, such as UTC itself orNorth American EST and EDT time zones. Supporting time zones at deeper levels ofdetail is up to the application. The rules for time adjustment across theworld are more political than rational, change frequently, and there is nostandard suitable for every application aside from UTC.
常數¶
datetime 模組匯出以下常數:
- datetime.UTC¶
Alias for the UTC time zone singleton
datetime.timezone.utc.在 3.11 版被加入.
Available Types¶
- classdatetime.date
An idealized naive date, assuming the current Gregorian calendar always was, andalways will be, in effect. Attributes:
year,month, andday.
- classdatetime.time
An idealized time, independent of any particular day, assuming that every dayhas exactly 24*60*60 seconds. (There is no notion of "leap seconds" here.)Attributes:
hour,minute,second,microsecond,andtzinfo.
- classdatetime.datetime
A combination of a date and a time. Attributes:
year,month,day,hour,minute,second,microsecond,andtzinfo.
- classdatetime.tzinfo
An abstract base class for time zone information objects. These are used by the
datetimeandtimeclasses to provide a customizable notion oftime adjustment (for example, to account for time zone and/or daylight savingtime).
- classdatetime.timezone
A class that implements the
tzinfoabstract base class as afixed offset from the UTC.在 3.2 版被加入.
Objects of these types are immutable.
Subclass relationships:
objecttimedeltatzinfotimezonetimedatedatetime
常見屬性¶
Thedate,datetime,time, andtimezone typesshare these common features:
Determining if an Object is Aware or Naive¶
Objects of thedate type are always naive.
An object of typetime ordatetime may be aware or naive.
Adatetime objectd is aware if both of the following hold:
d.tzinfo不是Noned.tzinfo.utcoffset(d)不會回傳None
否則d 會是 naive 的。
Atime objectt is aware if both of the following hold:
t.tzinfo不是Nonet.tzinfo.utcoffset(None)沒有回傳None。
否則t 會是 naive 的。
The distinction between aware and naive doesn't apply totimedeltaobjects.
timedelta 物件¶
一個timedelta 物件代表著一段持續時間,即兩個datetime 或date 之間的差異。
- classdatetime.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 integersor floats, and may be positive or negative.
Onlydays,seconds andmicroseconds are stored internally.Arguments are converted to those units:
一毫秒會被轉換為 1000 微秒。
一分鐘會被轉換為 60 秒。
一小時會被轉換為 3600 秒。
一週會被轉換為 7 天。
and days, seconds and microseconds are then normalized so that therepresentation is unique, with
0<=microseconds<10000000<=seconds<3600*24(the number of seconds in one day)-999999999<=days<=999999999
The following example illustrates how any arguments besidesdays,seconds andmicroseconds are "merged" and normalized into thosethree resulting attributes:
>>>fromdatetimeimporttimedelta>>>delta=timedelta(...days=50,...seconds=27,...microseconds=10,...milliseconds=29000,...minutes=5,...hours=8,...weeks=2...)>>># Only days, seconds, and microseconds remain>>>deltadatetime.timedelta(days=64, seconds=29156, microseconds=10)
If any argument is a float and there are fractional microseconds,the fractional microseconds left over from all arguments arecombined and their sum is rounded to the nearest microsecond usinground-half-to-even tiebreaker. If no argument is a float, theconversion and normalization processes are exact (no information islost).
If the normalized value of days lies outside the indicated range,
OverflowErroris raised.Note that normalization of negative values may be surprising at first. Forexample:
>>>fromdatetimeimporttimedelta>>>d=timedelta(microseconds=-1)>>>(d.days,d.seconds,d.microseconds)(-1, 86399, 999999)
Since the string representation of
timedeltaobjects can be confusing,use the following recipe to produce a more readable format:>>>defpretty_timedelta(td):...iftd.days>=0:...returnstr(td)...returnf'-({-td!s})'...>>>d=timedelta(hours=-1)>>>str(d)# not human-friendly'-1 day, 23:00:00'>>>pretty_timedelta(d)'-(1:00:00)'
類別屬性:
- timedelta.max¶
The most positive
timedeltaobject,timedelta(days=999999999,hours=23,minutes=59,seconds=59,microseconds=999999).
- timedelta.resolution¶
The smallest possible difference between non-equal
timedeltaobjects,timedelta(microseconds=1).
Note that, because of normalization,timedelta.max is greater than-timedelta.min.-timedelta.max is not representable as atimedelta object.
Instance attributes (read-only):
- timedelta.days¶
在 -999,999,999 到 999,999,999 (含)之間
- timedelta.seconds¶
在 0 到 86,399 (含)之間
警示
It is a somewhat common bug for code to unintentionally use this attributewhen it is actually intended to get a
total_seconds()value instead:>>>fromdatetimeimporttimedelta>>>duration=timedelta(seconds=11235813)>>>duration.days,duration.seconds(130, 3813)>>>duration.total_seconds()11235813.0
- timedelta.microseconds¶
在 0 到 999,999 (含)之間
Supported operations:
Operation | Result |
|---|---|
| Sum of |
| Difference of |
| Delta multiplied by an integer.Afterwards |
In general, | |
| Delta multiplied by a float. The result isrounded to the nearest multiple oftimedelta.resolution using round-half-to-even. |
| Division (3) of overall duration |
| Delta divided by a float or an int. The resultis rounded to the nearest multiple oftimedelta.resolution using round-half-to-even. |
| The floor is computed and the remainder (ifany) is thrown away. In the second case, aninteger is returned. (3) |
| The remainder is computed as a |
| Computes the quotient and the remainder: |
| Returns a |
| 等價於 |
| Equivalent to |
| Returns a string in the form |
| Returns a string representation of the |
註解:
這是精確的,但可能會溢位。
這是精確的,且不會溢位。
Division by zero raises
ZeroDivisionError.-timedelta.maxis not representable as atimedeltaobject.String representations of
timedeltaobjects are normalizedsimilarly to their internal representation. This leads to somewhatunusual results for negative timedeltas. For example:>>>timedelta(hours=-5)datetime.timedelta(days=-1, seconds=68400)>>>print(_)-1 day, 19:00:00
The expression
t2-t3will always be equal to the expressiont2+(-t3)exceptwhen t3 is equal totimedelta.max; in that case the former will produce a resultwhile the latter will overflow.
In addition to the operations listed above,timedelta objects supportcertain additions and subtractions withdate anddatetimeobjects (see below).
在 3.2 版的變更:Floor division and true division of atimedelta object by anothertimedelta object are now supported, as are remainder operations andthedivmod() function. True division and multiplication of atimedelta object by afloat object are now supported.
timedelta objects support equality and order comparisons.
In Boolean contexts, atimedelta object isconsidered to be true if and only if it isn't equal totimedelta(0).
實例方法:
- 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 thedivision form directly (e.g.td/timedelta(microseconds=1)).Note that for very large time intervals (greater than 270 years onmost platforms) this method will lose microsecond accuracy.
在 3.2 版被加入.
用法範例:timedelta¶
An additional example of normalization:
>>># Components of another_year add up to exactly 365 days>>>fromdatetimeimporttimedelta>>>year=timedelta(days=365)>>>another_year=timedelta(weeks=40,days=84,hours=23,...minutes=50,seconds=600)>>>year==another_yearTrue>>>year.total_seconds()31536000.0
Examples oftimedelta arithmetic:
>>>fromdatetimeimporttimedelta>>>year=timedelta(days=365)>>>ten_years=10*year>>>ten_yearsdatetime.timedelta(days=3650)>>>ten_years.days//36510>>>nine_years=ten_years-year>>>nine_yearsdatetime.timedelta(days=3285)>>>three_years=nine_years//3>>>three_years,three_years.days//365(datetime.timedelta(days=1095), 3)
date 物件¶
Adate object represents a date (year, month and day) in an idealizedcalendar, the current Gregorian calendar indefinitely extended in bothdirections.
January 1 of year 1 is called day number 1, January 2 of year 1 iscalled day number 2, and so on.[2]
- classdatetime.date(year,month,day)¶
All arguments are required. Arguments must be integers, in the followingranges:
MINYEAR<=year<=MAXYEAR1<=month<=121<=day<=numberofdaysinthegivenmonthandyear
If an argument outside those ranges is given,
ValueErroris raised.
Other constructors, all class methods:
- classmethoddate.today()¶
回傳目前的本地日期。
這等同於
date.fromtimestamp(time.time())。
- classmethoddate.fromtimestamp(timestamp)¶
Return the local date corresponding to the POSIX timestamp, such as isreturned by
time.time().This may raise
OverflowError, if the timestamp is outof the range of values supported by the platform Clocaltime()function, andOSErroronlocaltime()failure.It's common for this to be restricted to years from 1970 through 2038. Notethat on non-POSIX systems that include leap seconds in their notion of atimestamp, leap seconds are ignored byfromtimestamp().在 3.3 版的變更:Raise
OverflowErrorinstead ofValueErrorif the timestampis out of the range of values supported by the platform Clocaltime()function. RaiseOSErrorinstead ofValueErroronlocaltime()failure.
- classmethoddate.fromordinal(ordinal)¶
Return the date corresponding to the proleptic Gregorian ordinal, whereJanuary 1 of year 1 has ordinal 1.
ValueErroris raised unless1<=ordinal<=date.max.toordinal(). For any dated,date.fromordinal(d.toordinal())==d.
- classmethoddate.fromisoformat(date_string)¶
Return a
datecorresponding to adate_string given in any validISO 8601 format, with the following exceptions:Reduced precision dates are not currently supported (
YYYY-MM,YYYY).Extended date representations are not currently supported(
±YYYYYY-MM-DD).Ordinal dates are not currently supported (
YYYY-OOO).
範例:
>>>fromdatetimeimportdate>>>date.fromisoformat('2019-12-04')datetime.date(2019, 12, 4)>>>date.fromisoformat('20191204')datetime.date(2019, 12, 4)>>>date.fromisoformat('2021-W01-1')datetime.date(2021, 1, 4)
在 3.7 版被加入.
在 3.11 版的變更:Previously, this method only supported the format
YYYY-MM-DD.
- classmethoddate.fromisocalendar(year,week,day)¶
Return a
datecorresponding to the ISO calendar date specified byyear, week and day. This is the inverse of the functiondate.isocalendar().在 3.8 版被加入.
- classmethoddate.strptime(date_string,format)¶
Return a
datecorresponding todate_string, parsed according toformat. This is equivalent to:date(*(time.strptime(date_string,format)[0:3]))
ValueErroris raised if the date_string and formatcan't be parsed bytime.strptime()or if it returns a value which isn't atime tuple. See alsostrftime() 與 strptime() 的行為 anddate.fromisoformat().備註
Ifformat specifies a day of month without a year a
DeprecationWarningis emitted. This is to avoid a quadrennialleap year bug in code seeking to parse only a month and day as thedefault year used in absence of one in the format is not a leap year.Suchformat values may raise an error as of Python 3.15. Theworkaround is to always include a year in yourformat. If parsingdate_string values that do not have a year, explicitly add a year thatis a leap year before parsing:>>>fromdatetimeimportdate>>>date_string="02/29">>>when=date.strptime(f"{date_string};1984","%m/%d;%Y")# 避免閏年錯誤。>>>when.strftime("%B%d")'February 29'
在 3.14 版被加入.
類別屬性:
- 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).
Instance attributes (read-only):
- date.month¶
在 1 到 12 (含)之間。
- date.day¶
Between 1 and the number of days in the given month of the given year.
Supported operations:
Operation | Result |
|---|---|
|
|
| Computes |
| (3) |
date1==date2date1!=date2 | Equality comparison. (4) |
date1<date2date1>date2date1<=date2date1>=date2 | Order comparison. (5) |
註解:
date2 is moved forward in time if
timedelta.days>0, or backward iftimedelta.days<0. Afterwarddate2-date1==timedelta.days.timedelta.secondsandtimedelta.microsecondsare ignored.OverflowErroris raised ifdate2.yearwould be smaller thanMINYEARor larger thanMAXYEAR.timedelta.seconds和timedelta.microseconds被忽略。This is exact, and cannot overflow.
timedelta.secondsandtimedelta.microsecondsare 0, anddate2+timedelta==date1after.dateobjects are equal if they represent the same date.dateobjects that are not alsodatetimeinstancesare never equal todatetimeobjects, even if they representthe same date.date1 is considered less thandate2 whendate1 precedesdate2 in time.In other words,
date1<date2if and only ifdate1.toordinal()<date2.toordinal().Order comparison between a
dateobject that is not also adatetimeinstance and adatetimeobject raisesTypeError.
在 3.13 版的變更:Comparison betweendatetime object and an instance ofthedate subclass that is not adatetime subclassno longer converts the latter todate, ignoring the time partand the time zone.The default behavior can be changed by overriding the special comparisonmethods in subclasses.
In Boolean contexts, alldate objects are considered to be true.
實例方法:
- date.replace(year=self.year,month=self.month,day=self.day)¶
Return a new
dateobject with the same values, but with specifiedparameters updated.範例:
>>>fromdatetimeimportdate>>>d=date(2002,12,31)>>>d.replace(day=26)datetime.date(2002, 12, 26)
The generic function
copy.replace()also supportsdateobjects.
- date.timetuple()¶
回傳一個
time.struct_time,如同time.localtime()所回傳。The hours, minutes and seconds are 0, and the DST flag is -1.
d.timetuple()等價於: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()+1is 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 1has ordinal 1. For any
dateobjectd,date.fromordinal(d.toordinal())==d.
- date.weekday()¶
回傳一個代表星期幾的整數,星期一為 0、星期日為 6。例如
date(2002,12,4).weekday()==2為星期三。也請參考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 alsoweekday(),isocalendar().
- date.isocalendar()¶
Return anamed tuple object with three components:
year,weekandweekday.The ISO calendar is a widely used variant of the Gregorian calendar.[3]
The ISO year consists of 52 or 53 full weeks, and where a week starts on aMonday 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 weeknumber 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 2004begins on Monday, 29 Dec 2003 and ends on Sunday, 4 Jan 2004:
>>>fromdatetimeimportdate>>>date(2003,12,29).isocalendar()datetime.IsoCalendarDate(year=2004, week=1, weekday=1)>>>date(2004,1,4).isocalendar()datetime.IsoCalendarDate(year=2004, week=1, weekday=7)
在 3.9 版的變更:Result changed from a tuple to anamed tuple.
- date.isoformat()¶
回傳一以 ISO 8601 格式
YYYY-MM-DD表示的日期字串:>>>fromdatetimeimportdate>>>date(2002,12,4).isoformat()'2002-12-04'
- date.__str__()¶
For a date
d,str(d)is equivalent tod.isoformat().
- date.ctime()¶
Return a string representing the date:
>>>fromdatetimeimportdate>>>date(2002,12,4).ctime()'Wed Dec 4 00:00:00 2002'
d.ctime()等價於:time.ctime(time.mktime(d.timetuple()))
on platforms where the native C
ctime()function (whichtime.ctime()invokes, but whichdate.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.See alsostrftime() 與 strptime() 的行為 and
date.isoformat().
- date.__format__(format)¶
Same as
date.strftime(). This makes it possible to specify a formatstring for adateobject informatted stringliterals and when usingstr.format().See alsostrftime() 與 strptime() 的行為 anddate.isoformat().
用法範例:date¶
計算一個事件的天數的範例:
>>>importtime>>>fromdatetimeimportdate>>>today=date.today()>>>todaydatetime.date(2007, 12, 5)>>>today==date.fromtimestamp(time.time())True>>>my_birthday=date(today.year,6,24)>>>ifmy_birthday<today:...my_birthday=my_birthday.replace(year=today.year+1)...>>>my_birthdaydatetime.date(2008, 6, 24)>>>time_to_birthday=abs(my_birthday-today)>>>time_to_birthday.days202
更多date 的用法範例:
>>>fromdatetimeimportdate>>>d=date.fromordinal(730920)# 730920th day after 1. 1. 0001>>>ddatetime.date(2002, 3, 11)>>># Methods related to formatting string output>>>d.isoformat()'2002-03-11'>>>d.strftime("%d/%m/%y")'11/03/02'>>>d.strftime("%A%d. %B %Y")'Monday 11. March 2002'>>>d.ctime()'Mon Mar 11 00:00:00 2002'>>>'The{1} is {0:%d}, the{2} is {0:%B}.'.format(d,"day","month")'The day is 11, the month is March.'>>># Methods for to extracting 'components' under different calendars>>>t=d.timetuple()>>>foriint:...print(i)2002 # year3 # month11 # day0000 # weekday (0 = Monday)70 # 70th day in the year-1>>>ic=d.isocalendar()>>>foriinic:...print(i)2002 # ISO year11 # ISO week number1 # ISO day number ( 1 = Monday )>>># A date object is immutable; all operations produce a new object>>>d.replace(year=2005)datetime.date(2005, 3, 11)
datetime 物件¶
Adatetime object is a single object containing all the informationfrom adate object and atime object.
Like adate object,datetime assumes the current Gregoriancalendar extended in both directions; like atime object,datetime assumes there are exactly 3600*24 seconds in every day.
建構函式:
- classdatetime.datetime(year,month,day,hour=0,minute=0,second=0,microsecond=0,tzinfo=None,*,fold=0)¶
Theyear,month andday arguments are required.tzinfo may be
None, or aninstance of atzinfosubclass. The remaining arguments must be integersin the following ranges:MINYEAR<=year<=MAXYEAR,1<=month<=12,1<=day<=numberofdaysinthegivenmonthandyear,0<=hour<24,0<=minute<60,0<=second<60,0<=microsecond<1000000,foldin[0,1]。
If an argument outside those ranges is given,
ValueErroris raised.在 3.6 版的變更:新增fold 參數。
Other constructors, all class methods:
- classmethoddatetime.today()¶
回傳目前的本地日期與時間,且
tzinfo為None。等價於:
datetime.fromtimestamp(time.time())
也請見
now()、fromtimestamp()。This method is functionally equivalent to
now(), but without atzparameter.
- classmethoddatetime.now(tz=None)¶
Return the current local date and time.
如果選用的引數tz 為
None或未指定,則會像是today(),但盡可能提供比透過time.time()取得的時間戳記更多位數的資訊(例如,這在有提供 Cgettimeofday()函式的平台上可能可行)。Iftz is not
None, it must be an instance of atzinfosubclass,and the current date and time are converted totz’s time zone.This function is preferred over
today()andutcnow().備註
Subsequent calls to
datetime.now()may return the sameinstant depending on the precision of the underlying clock.
- classmethoddatetime.utcnow()¶
Return the current UTC date and time, with
tzinfoNone.This is like
now(), but returns the current UTC date and time, as a naivedatetimeobject. An aware current UTC datetime can be obtained bycallingdatetime.now(timezone.utc). See alsonow().警告
Because naive
datetimeobjects are treated by manydatetimemethodsas local times, it is preferred to use aware datetimes to represent timesin UTC. As such, the recommended way to create an object representing thecurrent time in UTC is by callingdatetime.now(timezone.utc).在 3.12 版之後被棄用:Use
datetime.now()withUTCinstead.
- classmethoddatetime.fromtimestamp(timestamp,tz=None)¶
Return the local date and time corresponding to the POSIX timestamp, such as isreturned by
time.time(). If optional argumenttz isNoneor notspecified, the timestamp is converted to the platform's local date and time, andthe returneddatetimeobject is naive.Iftz is not
None, it must be an instance of atzinfosubclass, and thetimestamp is converted totz’s time zone.fromtimestamp()may raiseOverflowError, if the timestamp is out ofthe range of values supported by the platform Clocaltime()orgmtime()functions, andOSErroronlocaltime()orgmtime()failure.It's common for this to be restricted to years in1970 through 2038. Note that on non-POSIX systems that include leap seconds intheir notion of a timestamp, leap seconds are ignored byfromtimestamp(),and then it's possible to have two timestamps differing by a second that yieldidenticaldatetimeobjects. This method is preferred overutcfromtimestamp().在 3.3 版的變更:Raise
OverflowErrorinstead ofValueErrorif the timestampis out of the range of values supported by the platform Clocaltime()orgmtime()functions. RaiseOSErrorinstead ofValueErroronlocaltime()orgmtime()failure.在 3.6 版的變更:
fromtimestamp()may return instances withfoldset to 1.
- classmethoddatetime.utcfromtimestamp(timestamp)¶
Return the UTC
datetimecorresponding to the POSIX timestamp, withtzinfoNone. (The resulting object is naive.)This may raise
OverflowError, if the timestamp isout of the range of values supported by the platform Cgmtime()function,andOSErrorongmtime()failure.It's common for this to be restricted to years in 1970 through 2038.To get an aware
datetimeobject, callfromtimestamp():datetime.fromtimestamp(timestamp,timezone.utc)
On the POSIX compliant platforms, it is equivalent to the followingexpression:
datetime(1970,1,1,tzinfo=timezone.utc)+timedelta(seconds=timestamp)
except the latter formula always supports the full years range: between
MINYEARandMAXYEARinclusive.警告
Because naive
datetimeobjects are treated by manydatetimemethodsas local times, it is preferred to use aware datetimes to represent timesin UTC. As such, the recommended way to create an object representing aspecific timestamp in UTC is by callingdatetime.fromtimestamp(timestamp,tz=timezone.utc).在 3.3 版的變更:Raise
OverflowErrorinstead ofValueErrorif the timestampis out of the range of values supported by the platform Cgmtime()function. RaiseOSErrorinstead ofValueErrorongmtime()failure.在 3.12 版之後被棄用:Use
datetime.fromtimestamp()withUTCinstead.
- classmethoddatetime.fromordinal(ordinal)¶
Return the
datetimecorresponding to the proleptic Gregorian ordinal,where January 1 of year 1 has ordinal 1.ValueErroris raised unless1<=ordinal<=datetime.max.toordinal(). The hour, minute, second andmicrosecond of the result are all 0, andtzinfoisNone.
- classmethoddatetime.combine(date,time,tzinfo=time.tzinfo)¶
Return a new
datetimeobject whose date components are equal to thegivendateobject's, and whose time componentsare equal to the giventimeobject's. If thetzinfoargument is provided, its value is used to set thetzinfoattributeof the result, otherwise thetzinfoattribute of thetime argumentis used. If thedate argument is adatetimeobject, its time componentsandtzinfoattributes are ignored.For any
datetimeobjectd,d==datetime.combine(d.date(),d.time(),d.tzinfo).在 3.6 版的變更:新增tzinfo 引數。
- classmethoddatetime.fromisoformat(date_string)¶
Return a
datetimecorresponding to adate_string in any validISO 8601 format, with the following exceptions:Time zone offsets may have fractional seconds.
The
Tseparator may be replaced by any single unicode character.Fractional hours and minutes are not supported.
Reduced precision dates are not currently supported (
YYYY-MM,YYYY).Extended date representations are not currently supported(
±YYYYYY-MM-DD).Ordinal dates are not currently supported (
YYYY-OOO).
範例:
>>>fromdatetimeimportdatetime>>>datetime.fromisoformat('2011-11-04')datetime.datetime(2011, 11, 4, 0, 0)>>>datetime.fromisoformat('20111104')datetime.datetime(2011, 11, 4, 0, 0)>>>datetime.fromisoformat('2011-11-04T00:05:23')datetime.datetime(2011, 11, 4, 0, 5, 23)>>>datetime.fromisoformat('2011-11-04T00:05:23Z')datetime.datetime(2011, 11, 4, 0, 5, 23, tzinfo=datetime.timezone.utc)>>>datetime.fromisoformat('20111104T000523')datetime.datetime(2011, 11, 4, 0, 5, 23)>>>datetime.fromisoformat('2011-W01-2T00:05:23.283')datetime.datetime(2011, 1, 4, 0, 5, 23, 283000)>>>datetime.fromisoformat('2011-11-04 00:05:23.283')datetime.datetime(2011, 11, 4, 0, 5, 23, 283000)>>>datetime.fromisoformat('2011-11-04 00:05:23.283+00:00')datetime.datetime(2011, 11, 4, 0, 5, 23, 283000, tzinfo=datetime.timezone.utc)>>>datetime.fromisoformat('2011-11-04T00:05:23+04:00')datetime.datetime(2011, 11, 4, 0, 5, 23, tzinfo=datetime.timezone(datetime.timedelta(seconds=14400)))
在 3.7 版被加入.
在 3.11 版的變更:Previously, this method only supported formats that could be emitted by
date.isoformat()ordatetime.isoformat().
- classmethoddatetime.fromisocalendar(year,week,day)¶
Return a
datetimecorresponding to the ISO calendar date specifiedby year, week and day. The non-date components of the datetime are populatedwith their normal default values. This is the inverse of the functiondatetime.isocalendar().在 3.8 版被加入.
- classmethoddatetime.strptime(date_string,format)¶
Return a
datetimecorresponding todate_string, parsed according toformat.Ifformat does not contain microseconds or time zone information, this is equivalent to:
datetime(*(time.strptime(date_string,format)[0:6]))
ValueErroris raised if the date_string and formatcan't be parsed bytime.strptime()or if it returns a value which isn't atime tuple. See alsostrftime() 與 strptime() 的行為 anddatetime.fromisoformat().在 3.13 版的變更:Ifformat specifies a day of month without a year a
DeprecationWarningis now emitted. This is to avoid a quadrennialleap year bug in code seeking to parse only a month and day as thedefault year used in absence of one in the format is not a leap year.Suchformat values may raise an error as of Python 3.15. Theworkaround is to always include a year in yourformat. If parsingdate_string values that do not have a year, explicitly add a year thatis a leap year before parsing:>>>fromdatetimeimportdatetime>>>date_string="02/29">>>when=datetime.strptime(f"{date_string};1984","%m/%d;%Y")# 避免閏年錯誤。>>>when.strftime("%B%d")'February 29'
類別屬性:
- datetime.resolution¶
The smallest possible difference between non-equal
datetimeobjects,timedelta(microseconds=1).
Instance attributes (read-only):
- 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 thetzinfo argument to the
datetimeconstructor,orNoneif none was passed.
- datetime.fold¶
In
[0,1]. Used to disambiguate wall times during a repeated interval. (Arepeated interval occurs when clocks are rolled back at the end of daylight savingtime or when the UTC offset for the current zone is decreased for political reasons.)The values 0 and 1 represent, respectively, the earlier and later of the twomoments with the same wall time representation.在 3.6 版被加入.
Supported operations:
Operation | Result |
|---|---|
| (1) |
| (2) |
| (3) |
datetime1==datetime2datetime1!=datetime2 | Equality comparison. (4) |
datetime1<datetime2datetime1>datetime2datetime1<=datetime2datetime1>=datetime2 | Order comparison. (5) |
datetime2is a duration oftimedeltaremoved fromdatetime1, moving forward intime iftimedelta.days>0, or backward iftimedelta.days<0. Theresult has the sametzinfoattribute as the input datetime, anddatetime2-datetime1==timedeltaafter.OverflowErroris raised ifdatetime2.yearwould be smaller thanMINYEARor larger thanMAXYEAR. Note that no time zone adjustments are done even if theinput is an aware object.Computes the
datetime2such thatdatetime2+timedelta==datetime1. As foraddition, the result has the sametzinfoattribute as the inputdatetime, and no time zone adjustments are done even if the input is aware.Subtraction of a
datetimefrom adatetimeis defined only ifboth operands are naive, or if both are aware. If one is aware and the other isnaive,TypeErroris raised.If both are naive, or both are aware and have the same
tzinfoattribute,thetzinfoattributes are ignored, and the result is atimedeltaobjecttsuch thatdatetime2+t==datetime1. No time zone adjustmentsare done in this case.If both are aware and have different
tzinfoattributes,a-bactsas ifaandbwere first converted to naive UTC datetimes. Theresult is(a.replace(tzinfo=None)-a.utcoffset())-(b.replace(tzinfo=None)-b.utcoffset())except that the implementation never overflows.datetimeobjects are equal if they represent the same dateand time, taking into account the time zone.Naive and aware
datetimeobjects are never equal.If both comparands are aware, and have the same
tzinfoattribute,thetzinfoandfoldattributes are ignored andthe base datetimes are compared.If both comparands are aware and have differenttzinfoattributes, the comparison acts as comparands were first converted to UTCdatetimes except that the implementation never overflows.datetimeinstances in a repeated interval are never equal todatetimeinstances in other time zone.datetime1 is considered less thandatetime2 whendatetime1 precedesdatetime2 in time, taking into account the time zone.
Order comparison between naive and aware
datetimeobjectsraisesTypeError.If both comparands are aware, and have the same
tzinfoattribute,thetzinfoandfoldattributes are ignored andthe base datetimes are compared.If both comparands are aware and have differenttzinfoattributes, the comparison acts as comparands were first converted to UTCdatetimes except that the implementation never overflows.
在 3.13 版的變更:Comparison betweendatetime object and an instance ofthedate subclass that is not adatetime subclassno longer converts the latter todate, ignoring the time partand the time zone.The default behavior can be changed by overriding the special comparisonmethods in subclasses.
實例方法:
- datetime.time()¶
Return
timeobject with same hour, minute, second, microsecond and fold.tzinfoisNone. See also methodtimetz().在 3.6 版的變更:The fold value is copied to the returned
timeobject.
- datetime.timetz()¶
Return
timeobject with same hour, minute, second, microsecond, fold, andtzinfo attributes. See also methodtime().在 3.6 版的變更:The fold value is copied to the returned
timeobject.
- 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 new
datetimeobject with the same attributes, but withspecified parameters updated. Note thattzinfo=Nonecan be specified tocreate a naive datetime from an aware datetime with no conversion of dateand time data.datetimeobjects are also supported by generic functioncopy.replace().在 3.6 版的變更:新增fold 參數。
- datetime.astimezone(tz=None)¶
Return a
datetimeobject with newtzinfoattributetz,adjusting the date and time data so the result is the same UTC time asself, but intz's local time.If provided,tz must be an instance of a
tzinfosubclass, and itsutcoffset()anddst()methods must not returnNone. Ifselfis naive, it is presumed to represent time in the system time zone.If called without arguments (or with
tz=None) the system localtime zone is assumed for the target time zone. The.tzinfoattribute of the converteddatetime instance will be set to an instance oftimezonewith the zone name and offset obtained from the OS.If
self.tzinfoistz,self.astimezone(tz)is equal toself: noadjustment of date or time data is performed. Else the result is localtime in the time zonetz, representing the same UTC time asself: afterastz=dt.astimezone(tz),astz-astz.utcoffset()will havethe same date and time data asdt-dt.utcoffset().If you merely want to attach a
timezoneobjecttz to a datetimedt withoutadjustment of date and time data, usedt.replace(tzinfo=tz). If youmerely want to remove thetimezoneobject from an aware datetimedt withoutconversion of date and time data, usedt.replace(tzinfo=None).Note that the default
tzinfo.fromutc()method can be overridden in atzinfosubclass to affect the result returned byastimezone().Ignoring error cases,astimezone()acts like:defastimezone(self,tz):ifself.tzinfoistz:returnself# Convert self to UTC, and attach the new timezone object.utc=(self-self.utcoffset()).replace(tzinfo=tz)# Convert from UTC to tz's local time.returntz.fromutc(utc)
在 3.3 版的變更:tz now can be omitted.
在 3.6 版的變更:The
astimezone()method can now be called on naive instances thatare presumed to represent system local time.
- datetime.utcoffset()¶
If
tzinfoisNone, returnsNone, else returnsself.tzinfo.utcoffset(self), and raises an exception if the latter doesn'treturnNoneor atimedeltaobject with magnitude less than one day.在 3.7 版的變更:The UTC offset is not restricted to a whole number of minutes.
- datetime.dst()¶
If
tzinfoisNone, returnsNone, else returnsself.tzinfo.dst(self), and raises an exception if the latter doesn't returnNoneor atimedeltaobject with magnitude less than one day.在 3.7 版的變更:The DST offset is not restricted to a whole number of minutes.
- datetime.tzname()¶
If
tzinfoisNone, returnsNone, else returnsself.tzinfo.tzname(self), raises an exception if the latter doesn't returnNoneor a string object,
- datetime.timetuple()¶
回傳一個
time.struct_time,如同time.localtime()所回傳。d.timetuple()等價於: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()+1is the day number within the current year starting with 1 for January1st. Thetm_isdstflag of the result is set according to thedst()method:tzinfoisNoneordst()returnsNone,tm_isdstis set to-1; else ifdst()returns anon-zero value,tm_isdstis set to 1; elsetm_isdstisset to 0.
- datetime.utctimetuple()¶
If
datetimeinstancedis naive, this is the same asd.timetuple()except thattm_isdstis forced to 0 regardless of whatd.dst()returns. DST is never in effect for a UTC time.If
dis aware,dis normalized to UTC time, by subtractingd.utcoffset(), and atime.struct_timefor thenormalized time is returned.tm_isdstis forced to 0. Notethat anOverflowErrormay be raised ifd.yearwasMINYEARorMAXYEARand UTC adjustment spills over a yearboundary.警告
Because naive
datetimeobjects are treated by manydatetimemethodsas local times, it is preferred to use aware datetimes to represent timesin UTC; as a result, usingdatetime.utctimetuple()may give misleadingresults. If you have a naivedatetimerepresenting UTC, usedatetime.replace(tzinfo=timezone.utc)to make it aware, at which pointyou can usedatetime.timetuple().
- datetime.toordinal()¶
Return the proleptic Gregorian ordinal of the date. The same as
self.date().toordinal().
- datetime.timestamp()¶
Return POSIX timestamp corresponding to the
datetimeinstance. The return value is afloatsimilar to thatreturned bytime.time().Naive
datetimeinstances are assumed to represent localtime and this method relies on the platform Cmktime()function to perform the conversion. Sincedatetimesupports wider range of values thanmktime()on manyplatforms, this method may raiseOverflowErrororOSErrorfor times far in the past or far in the future.For aware
datetimeinstances, the return value is computedas:(dt-datetime(1970,1,1,tzinfo=timezone.utc)).total_seconds()
在 3.3 版被加入.
在 3.6 版的變更:The
timestamp()method uses thefoldattribute todisambiguate the times during a repeated interval.備註
There is no method to obtain the POSIX timestamp directly from anaive
datetimeinstance representing UTC time. If yourapplication uses this convention and your system time zone is notset to UTC, you can obtain the POSIX timestamp by supplyingtzinfo=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 alsoisoweekday().
- 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 alsoweekday(),isocalendar().
- datetime.isocalendar()¶
Return anamed tuple with three components:
year,weekandweekday. The same asself.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,如果microsecond不是 0YYYY-MM-DDTHH:MM:SS,如果microsecond是 0
如果
utcoffset()没有回傳None,則會附加一个字串,給出 UTC 偏移:YYYY-MM-DDTHH:MM:SS.ffffff+HH:MM[:SS[.ffffff]],如果microsecond不是 0YYYY-MM-DDTHH:MM:SS+HH:MM[:SS[.ffffff]],如果microsecond是 0
範例:
>>>fromdatetimeimportdatetime,timezone>>>datetime(2019,5,18,15,17,8,132263).isoformat()'2019-05-18T15:17:08.132263'>>>datetime(2019,5,18,15,17,tzinfo=timezone.utc).isoformat()'2019-05-18T15:17:00+00:00'
The optional argumentsep (default
'T') is a one-character separator,placed between the date and time portions of the result. For example:>>>fromdatetimeimporttzinfo,timedelta,datetime>>>classTZ(tzinfo):..."""A time zone with an arbitrary, constant -06:39 offset."""...defutcoffset(self,dt):...returntimedelta(hours=-6,minutes=-39)...>>>datetime(2002,12,25,tzinfo=TZ()).isoformat(' ')'2002-12-25 00:00:00-06:39'>>>datetime(2009,11,27,microsecond=100,tzinfo=TZ()).isoformat()'2009-11-27T00:00:00.000100-06:39'
The optional argumenttimespec specifies the number of additionalcomponents of the time to include (the default is
'auto').It can be one of the following:'auto': Same as'seconds'ifmicrosecondis 0,same as'microseconds'otherwise.'hours': Include thehourin the two-digitHHformat.'milliseconds': Include full time, but truncate fractional secondpart to milliseconds.HH:MM:SS.sssformat.'microseconds': Include full time inHH:MM:SS.ffffffformat.
備註
Excluded time components are truncated, not rounded.
ValueErrorwill be raised on an invalidtimespec argument:>>>fromdatetimeimportdatetime>>>datetime.now().isoformat(timespec='minutes')'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 版的變更:新增timespec 參數。
- datetime.ctime()¶
Return a string representing the date and time:
>>>fromdatetimeimportdatetime>>>datetime(2002,12,4,20,30,40).ctime()'Wed Dec 4 20:30:40 2002'
The output string willnot include time zone information, regardlessof whether the input is aware or naive.
d.ctime()等價於:time.ctime(time.mktime(d.timetuple()))
on platforms where the native C
ctime()function(whichtime.ctime()invokes, but whichdatetime.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.See alsostrftime() 與 strptime() 的行為 and
datetime.isoformat().
- datetime.__format__(format)¶
Same as
datetime.strftime(). This makes it possible to specify a formatstring for adatetimeobject informatted stringliterals and when usingstr.format().See alsostrftime() 與 strptime() 的行為 anddatetime.isoformat().
用法範例:datetime¶
更多datetime 的用法範例:
>>>fromdatetimeimportdatetime,date,time,timezone>>># 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()>>>datetime.now()datetime.datetime(2007, 12, 6, 16, 29, 43, 79043) # GMT +1>>>datetime.now(timezone.utc)datetime.datetime(2007, 12, 6, 15, 29, 43, 79060, tzinfo=datetime.timezone.utc)>>># Using datetime.strptime()>>>dt=datetime.strptime("21/11/06 16:30","%d/%m/%y %H:%M")>>>dtdatetime.datetime(2006, 11, 21, 16, 30)>>># Using datetime.timetuple() to get tuple of all attributes>>>tt=dt.timetuple()>>>foritintt:...print(it)...2006 # year11 # month21 # day16 # hour30 # minute0 # second1 # weekday (0 = Monday)325 # number of days since 1st January-1 # dst - method tzinfo.dst() returned None>>># Date in ISO format>>>ic=dt.isocalendar()>>>foritinic:...print(it)...2006 # ISO year47 # ISO week2 # ISO weekday>>># Formatting a 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.'
The example below defines atzinfo subclass capturing time zoneinformation for Kabul, Afghanistan, which used +4 UTC until 1945and then +4:30 UTC thereafter:
fromdatetimeimporttimedelta,datetime,tzinfo,timezoneclassKabulTz(tzinfo):# Kabul used +4 until 1945, when they moved to +4:30UTC_MOVE_DATE=datetime(1944,12,31,20,tzinfo=timezone.utc)defutcoffset(self,dt):ifdt.year<1945:returntimedelta(hours=4)elif(1945,1,1,0,0)<=dt.timetuple()[:5]<(1945,1,1,0,30):# An ambiguous ("imaginary") half-hour range representing# a 'fold' in time due to the shift from +4 to +4:30.# If dt falls in the imaginary range, use fold to decide how# to resolve. See PEP495.returntimedelta(hours=4,minutes=(30ifdt.foldelse0))else:returntimedelta(hours=4,minutes=30)deffromutc(self,dt):# Follow same validations as in datetime.tzinfoifnotisinstance(dt,datetime):raiseTypeError("fromutc() requires a datetime argument")ifdt.tzinfoisnotself:raiseValueError("dt.tzinfo is not self")# A custom implementation is required for fromutc as# the input to this function is a datetime with utc values# but with a tzinfo set to self.# See datetime.astimezone or fromtimestamp.ifdt.replace(tzinfo=timezone.utc)>=self.UTC_MOVE_DATE:returndt+timedelta(hours=4,minutes=30)else:returndt+timedelta(hours=4)defdst(self,dt):# Kabul does not observe daylight saving time.returntimedelta(0)deftzname(self,dt):ifdt>=self.UTC_MOVE_DATE:return"+04:30"return"+04"
Usage ofKabulTz from above:
>>>tz1=KabulTz()>>># Datetime before the change>>>dt1=datetime(1900,11,21,16,30,tzinfo=tz1)>>>print(dt1.utcoffset())4:00:00>>># Datetime after the change>>>dt2=datetime(2006,6,14,13,0,tzinfo=tz1)>>>print(dt2.utcoffset())4:30:00>>># Convert datetime to another time zone>>>dt3=dt2.astimezone(timezone.utc)>>>dt3datetime.datetime(2006, 6, 14, 8, 30, tzinfo=datetime.timezone.utc)>>>dt2datetime.datetime(2006, 6, 14, 13, 0, tzinfo=KabulTz())>>>dt2==dt3True
time 物件¶
Atime object represents a (local) time of day, independent of any particularday, and subject to adjustment via atzinfo object.
- classdatetime.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 atzinfosubclass. The remaining arguments must be integers in thefollowing ranges:0<=hour<24,0<=minute<60,0<=second<60,0<=microsecond<1000000,foldin[0,1]。
If an argument outside those ranges is given,
ValueErroris raised. Alldefault to 0 excepttzinfo, which defaults toNone.
類別屬性:
- time.resolution¶
The smallest possible difference between non-equal
timeobjects,timedelta(microseconds=1), although note that arithmetic ontimeobjects is not supported.
Instance attributes (read-only):
- 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
timeconstructor, orNoneif none was passed.
- time.fold¶
In
[0,1]. Used to disambiguate wall times during a repeated interval. (Arepeated interval occurs when clocks are rolled back at the end of daylight savingtime or when the UTC offset for the current zone is decreased for political reasons.)The values 0 and 1 represent, respectively, the earlier and later of the twomoments with the same wall time representation.在 3.6 版被加入.
time objects support equality and order comparisons,wherea is considered less thanb whena precedesb in time.
Naive and awaretime objects are never equal.Order comparison between naive and awaretime objects raisesTypeError.
If both comparands are aware, and have the sametzinfoattribute, thetzinfo andfold attributes areignored and the base times are compared. If both comparands are aware andhave differenttzinfo attributes, the comparands are first adjusted bysubtracting their UTC offsets (obtained fromself.utcoffset()).
In Boolean contexts, atime object is always considered to be true.
在 3.5 版的變更:Before Python 3.5, atime object was considered to be false if itrepresented midnight in UTC. This behavior was considered obscure anderror-prone and has been removed in Python 3.5. Seebpo-13936 for fulldetails.
其他建構函式:
- classmethodtime.fromisoformat(time_string)¶
Return a
timecorresponding to atime_string in any validISO 8601 format, with the following exceptions:Time zone offsets may have fractional seconds.
The leading
T, normally required in cases where there may be ambiguity betweena date and a time, is not required.Fractional seconds may have any number of digits (anything beyond 6 willbe truncated).
Fractional hours and minutes are not supported.
範例:
>>>fromdatetimeimporttime>>>time.fromisoformat('04:23:01')datetime.time(4, 23, 1)>>>time.fromisoformat('T04:23:01')datetime.time(4, 23, 1)>>>time.fromisoformat('T042301')datetime.time(4, 23, 1)>>>time.fromisoformat('04:23:01.000384')datetime.time(4, 23, 1, 384)>>>time.fromisoformat('04:23:01,000384')datetime.time(4, 23, 1, 384)>>>time.fromisoformat('04:23:01+04:00')datetime.time(4, 23, 1, tzinfo=datetime.timezone(datetime.timedelta(seconds=14400)))>>>time.fromisoformat('04:23:01Z')datetime.time(4, 23, 1, tzinfo=datetime.timezone.utc)>>>time.fromisoformat('04:23:01+00:00')datetime.time(4, 23, 1, tzinfo=datetime.timezone.utc)
在 3.7 版被加入.
在 3.11 版的變更:Previously, this method only supported formats that could be emitted by
time.isoformat().
- classmethodtime.strptime(date_string,format)¶
Return a
timecorresponding todate_string, parsed according toformat.Ifformat does not contain microseconds or timezone information, this is equivalent to:
time(*(time.strptime(date_string,format)[3:6]))
ValueErroris raised if thedate_string andformatcannot be parsed bytime.strptime()or if it returns a value which is not atime tuple. See alsostrftime() 與 strptime() 的行為 andtime.fromisoformat().在 3.14 版被加入.
實例方法:
- time.replace(hour=self.hour,minute=self.minute,second=self.second,microsecond=self.microsecond,tzinfo=self.tzinfo,*,fold=0)¶
Return a new
timewith the same values, but with specifiedparameters updated. Note thattzinfo=Nonecan be specified to create anaivetimefrom an awaretime, without conversion of thetime data.timeobjects are also supported by generic functioncopy.replace().在 3.6 版的變更:新增fold 參數。
- time.isoformat(timespec='auto')¶
Return a string representing the time in ISO 8601 format, one of:
HH:MM:SS.ffffff, ifmicrosecondis not 0HH:MM:SS, ifmicrosecondis 0HH:MM:SS.ffffff+HH:MM[:SS[.ffffff]], ifutcoffset()does not returnNoneHH:MM:SS+HH:MM[:SS[.ffffff]], ifmicrosecondis 0 andutcoffset()does not returnNone
The optional argumenttimespec specifies the number of additionalcomponents of the time to include (the default is
'auto').It can be one of the following:'auto': Same as'seconds'ifmicrosecondis 0,same as'microseconds'otherwise.'hours': Include thehourin the two-digitHHformat.'milliseconds': Include full time, but truncate fractional secondpart to milliseconds.HH:MM:SS.sssformat.'microseconds': Include full time inHH:MM:SS.ffffffformat.
備註
Excluded time components are truncated, not rounded.
ValueErrorwill be raised on an invalidtimespec argument.範例:
>>>fromdatetimeimporttime>>>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 版的變更:新增timespec 參數。
- time.__str__()¶
For a time
t,str(t)is equivalent tot.isoformat().
- time.strftime(format)¶
Return a string representing the time, controlled by an explicit formatstring. See alsostrftime() 與 strptime() 的行為 and
time.isoformat().
- time.__format__(format)¶
Same as
time.strftime(). This makes it possible to specifya format string for atimeobject informatted stringliterals and when usingstr.format().See alsostrftime() 與 strptime() 的行為 andtime.isoformat().
- time.utcoffset()¶
If
tzinfoisNone, returnsNone, else returnsself.tzinfo.utcoffset(None), and raises an exception if the latter doesn'treturnNoneor atimedeltaobject with magnitude less than one day.在 3.7 版的變更:The UTC offset is not restricted to a whole number of minutes.
- time.dst()¶
If
tzinfoisNone, returnsNone, else returnsself.tzinfo.dst(None), and raises an exception if the latter doesn't returnNone, or atimedeltaobject with magnitude less than one day.在 3.7 版的變更:The DST offset is not restricted to a whole number of minutes.
- time.tzname()¶
If
tzinfoisNone, returnsNone, else returnsself.tzinfo.tzname(None), or raises an exception if the latter doesn'treturnNoneor a string object.
用法範例:time¶
Examples of working with atime object:
>>>fromdatetimeimporttime,tzinfo,timedelta>>>classTZ1(tzinfo):...defutcoffset(self,dt):...returntimedelta(hours=1)...defdst(self,dt):...returntimedelta(0)...deftzname(self,dt):...return"+01:00"...def__repr__(self):...returnf"{self.__class__.__name__}()"...>>>t=time(12,10,30,tzinfo=TZ1())>>>tdatetime.time(12, 10, 30, tzinfo=TZ1())>>>t.isoformat()'12:10:30+01:00'>>>t.dst()datetime.timedelta(0)>>>t.tzname()'+01:00'>>>t.strftime("%H:%M:%S %Z")'12:10:30 +01:00'>>>'The{} is {:%H:%M}.'.format("time",t)'The time is 12:10.'
tzinfo 物件¶
- classdatetime.tzinfo¶
This is an abstract base class, meaning that this class should not beinstantiated directly. Define a subclass of
tzinfoto captureinformation about a particular time zone.An instance of (a concrete subclass of)
tzinfocan be passed to theconstructors fordatetimeandtimeobjects. The latter objectsview their attributes as being in local time, and thetzinfoobjectsupports methods revealing offset of local time from UTC, the name of the timezone, and DST offset, all relative to a date or time object passed to them.You need to derive a concrete subclass, and (at least)supply implementations of the standard
tzinfomethods needed by thedatetimemethods you use. Thedatetimemodule providestimezone, a simple concrete subclass oftzinfowhich canrepresent time zones with fixed offset from UTC such as UTC itself or NorthAmerican EST and EDT.Special requirement for pickling: A
tzinfosubclass must have an__init__()method that can be called with no arguments,otherwise it can bepickled but possibly not unpickled again. This is a technical requirement thatmay be relaxed in the future.A concrete subclass of
tzinfomay need to implement the followingmethods. Exactly which methods are needed depends on the uses made of awaredatetimeobjects. If in doubt, simply implement all of them.
- tzinfo.utcoffset(dt)¶
Return offset of local time from UTC, as a
timedeltaobject that ispositive east of UTC. If local time is west of UTC, this should be negative.This represents thetotal offset from UTC; for example, if a
tzinfoobject represents both time zone and DST adjustments,utcoffset()should return their sum. If the UTC offset isn't known,returnNone. Else the value returned must be atimedeltaobjectstrictly between-timedelta(hours=24)andtimedelta(hours=24)(the magnitude of the offset must be less than one day). Most implementationsofutcoffset()will probably look like one of these two:returnCONSTANT# fixed-offset classreturnCONSTANT+self.dst(dt)# daylight-aware class
If
utcoffset()does not returnNone,dst()should not returnNoneeither.The default implementation of
utcoffset()raisesNotImplementedError.在 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
timedeltaobject orNoneif DST information isn't known.Return
timedelta(0)if DST is not in effect.If DST is in effect, return the offset as atimedeltaobject(seeutcoffset()for details). Note that DST offset, if applicable, hasalready been added to the UTC offset returned byutcoffset(), so there'sno need to consultdst()unless you're interested in obtaining DST infoseparately. For example,datetime.timetuple()calls itstzinfoattribute'sdst()method to determine how thetm_isdstflagshould be set, andtzinfo.fromutc()callsdst()to account forDST changes when crossing time zones.An instancetz of a
tzinfosubclass that models both standard anddaylight times must be consistent in this sense:tz.utcoffset(dt)-tz.dst(dt)must return the same result for every
datetimedt withdt.tzinfo==tz. For sanetzinfosubclasses, this expression yields the timezone's "standard offset", which should not depend on the date or the time, butonly on geographic location. The implementation ofdatetime.astimezone()relies on this, but cannot detect violations; it's the programmer'sresponsibility to ensure it. If atzinfosubclass cannot guaranteethis, it may be able to override the default implementation oftzinfo.fromutc()to work correctly withastimezone()regardless.Most implementations of
dst()will probably look like one of these two:defdst(self,dt):# a fixed-offset class: doesn't account for DSTreturntimedelta(0)
或是:
defdst(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.ifdston<=dt.replace(tzinfo=None)<dstoff:returntimedelta(hours=1)else:returntimedelta(0)
The default implementation of
dst()raisesNotImplementedError.在 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
datetimeobjectdt, asa string. Nothing about string names is defined by thedatetimemodule,and there's no requirement that it mean anything in particular. For example,"GMT","UTC","-500","-5:00","EDT","US/Eastern","America/NewYork"are allvalid replies. ReturnNoneif a string name isn't known. Note that this isa method rather than a fixed string primarily because sometzinfosubclasses will wish to return different names depending on the specific valueofdt passed, especially if thetzinfoclass is accounting fordaylight time.The default implementation of
tzname()raisesNotImplementedError.
These methods are called by adatetime ortime object, inresponse to their methods of the same names. Adatetime object passesitself as the argument, and atime object passesNone as theargument. Atzinfo subclass's methods should therefore be prepared toaccept adt argument ofNone, or of classdatetime.
WhenNone is passed, it's up to the class designer to decide the bestresponse. For example, returningNone is appropriate if the class wishes tosay that time objects don't participate in thetzinfo protocols. Itmay be more useful forutcoffset(None) to return the standard UTC offset, asthere is no other convention for discovering the standard offset.
When adatetime object is passed in response to adatetimemethod,dt.tzinfo is the same object asself.tzinfo methods canrely on this, unless user code callstzinfo methods directly. Theintent is that thetzinfo methods interpretdt as being in localtime, and not need worry about objects in other time zones.
There is one moretzinfo method that a subclass may wish to override:
- tzinfo.fromutc(dt)¶
This is called from the default
datetime.astimezone()implementation. When called from that,dt.tzinfoisself, anddt'sdate and time data are to be viewed as expressing a UTC time. The purposeoffromutc()is to adjust the date and time data, returning anequivalent datetime inself's local time.Most
tzinfosubclasses should be able to inherit the defaultfromutc()implementation without problems. It's strong enough to handlefixed-offset time zones, and time zones accounting for both standard anddaylight time, and the latter even if the DST transition times differ indifferent years. An example of a time zone the defaultfromutc()implementation may not handle correctly in all cases is one where the standardoffset (from UTC) depends on the specific date and time passed, which can happenfor political reasons. The default implementations ofastimezone()andfromutc()may not produce the result you want if the result is one of thehours straddling the moment the standard offset changes.Skipping code for error cases, the default
fromutc()implementation actslike:deffromutc(self,dt):# raise ValueError error if dt.tzinfo is not selfdtoff=dt.utcoffset()dtdst=dt.dst()# raise ValueError if dtoff is None or dtdst is Nonedelta=dtoff-dtdst# this is self's standard offsetifdelta:dt+=delta# convert to standard local timedtdst=dt.dst()# raise ValueError if dtdst is Noneifdtdst:returndt+dtdstelse:returndt
In the followingtzinfo_examples.py file there are some examples oftzinfo classes:
fromdatetimeimporttzinfo,timedelta,datetimeZERO=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.)importtimeas_timeSTDOFFSET=timedelta(seconds=-_time.timezone)if_time.daylight:DSTOFFSET=timedelta(seconds=-_time.altzone)else:DSTOFFSET=STDOFFSETDSTDIFF=DSTOFFSET-STDOFFSETclassLocalTimezone(tzinfo):deffromutc(self,dt):assertdt.tzinfoisselfstamp=(dt-datetime(1970,1,1,tzinfo=self))//SECONDargs=_time.localtime(stamp)[:6]dst_diff=DSTDIFF//SECOND# Detect foldfold=(args==_time.localtime(stamp-dst_diff))returndatetime(*args,microsecond=dt.microsecond,tzinfo=self,fold=fold)defutcoffset(self,dt):ifself._isdst(dt):returnDSTOFFSETelse:returnSTDOFFSETdefdst(self,dt):ifself._isdst(dt):returnDSTDIFFelse:returnZEROdeftzname(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)returntt.tm_isdst>0Local=LocalTimezone()# A complete implementation of current DST rules for major US time zones.deffirst_sunday_on_or_after(dt):days_to_go=6-dt.weekday()ifdays_to_go:dt+=timedelta(days_to_go)returndt# 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# https://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_2006defus_dst_range(year):# Find start and end times for US DST. For years before 1967, return# start = end for no DST.if2006<year:dststart,dstend=DSTSTART_2007,DSTEND_2007elif1986<year<2007:dststart,dstend=DSTSTART_1987_2006,DSTEND_1987_2006elif1966<year<1987:dststart,dstend=DSTSTART_1967_1986,DSTEND_1967_1986else:return(datetime(year,1,1),)*2start=first_sunday_on_or_after(dststart.replace(year=year))end=first_sunday_on_or_after(dstend.replace(year=year))returnstart,endclassUSTimeZone(tzinfo):def__init__(self,hours,reprname,stdname,dstname):self.stdoffset=timedelta(hours=hours)self.reprname=reprnameself.stdname=stdnameself.dstname=dstnamedef__repr__(self):returnself.reprnamedeftzname(self,dt):ifself.dst(dt):returnself.dstnameelse:returnself.stdnamedefutcoffset(self,dt):returnself.stdoffset+self.dst(dt)defdst(self,dt):ifdtisNoneordt.tzinfoisNone:# 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.returnZEROassertdt.tzinfoisselfstart,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)ifstart+HOUR<=dt<end-HOUR:# DST is in effect.returnHOURifend-HOUR<=dt<end:# Fold (an ambiguous hour): use dt.fold to disambiguate.returnZEROifdt.foldelseHOURifstart<=dt<start+HOUR:# Gap (a non-existent hour): reverse the fold rule.returnHOURifdt.foldelseZERO# DST is off.returnZEROdeffromutc(self,dt):assertdt.tzinfoisselfstart,end=us_dst_range(dt.year)start=start.replace(tzinfo=self)end=end.replace(tzinfo=self)std_time=dt+self.stdoffsetdst_time=std_time+HOURifend<=dst_time<end+HOUR:# Repeated hourreturnstd_time.replace(fold=1)ifstd_time<startordst_time>=end:# Standard timereturnstd_timeifstart<=std_time<end-HOUR:# Daylight saving timereturndst_timeEastern=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 atzinfosubclass accounting for both standard and daylight time, at the DST transitionpoints. For concreteness, consider US Eastern (UTC -0500), where EDT begins theminute after 1:59 (EST) on the second Sunday in March, and ends the minute after1:59 (EDT) on the first Sunday in November:
UTC3:MM4:MM5:MM6:MM7:MM8:MMEST22:MM23:MM0:MM1:MM2:MM3:MMEDT23:MM0:MM1:MM2:MM3:MM4:MMstart22:MM23:MM0:MM1:MM3:MM4:MMend23:MM0:MM1:MM1:MM2:MM3:MM
When DST starts (the "start" line), the local wall clock leaps from 1:59 to3:00. A wall time of the form 2:MM doesn't really make sense on that day, soastimezone(Eastern) won't deliver a result withhour==2 on the day DSTbegins. For example, at the Spring forward transition of 2016, we get:
>>>fromdatetimeimportdatetime,timezone>>>fromtzinfo_examplesimportHOUR,Eastern>>>u0=datetime(2016,3,13,5,tzinfo=timezone.utc)>>>foriinrange(4):...u=u0+i*HOUR...t=u.astimezone(Eastern)...print(u.time(),'UTC =',t.time(),t.tzname())...05:00:00 UTC = 00:00:00 EST06:00:00 UTC = 01:00:00 EST07:00:00 UTC = 03:00:00 EDT08:00:00 UTC = 04:00:00 EDT
When DST ends (the "end" line), there's a potentially worse problem: there's anhour that can't be spelled unambiguously in local wall time: the last hour ofdaylight time. In Eastern, that's times of the form 5:MM UTC on the daydaylight time ends. The local wall clock leaps from 1:59 (daylight time) backto 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 UTChours into the same local hour then. In the Eastern example, UTC times of theform 5:MM and 6:MM both map to 1:MM when converted to Eastern, but earlier timeshave thefold 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)>>>foriinrange(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 005:00:00 UTC = 01:00:00 EDT 006:00:00 UTC = 01:00:00 EST 107:00:00 UTC = 02:00:00 EST 0
Note that thedatetime instances that differ only by the value of thefold attribute are considered equal in comparisons.
Applications that can't bear wall-time ambiguities should explicitly check thevalue of thefold attribute or avoid using hybridtzinfo subclasses; there are no ambiguities when usingtimezone,or any other fixed-offsettzinfo subclass (such as a class representingonly EST (fixed offset -5 hours), or only EDT (fixed offset -4 hours)).
也參考
zoneinfoThe
datetimemodule has a basictimezoneclass (forhandling arbitrary fixed offsets from UTC) and itstimezone.utcattribute (a UTCtimezoneinstance).
zoneinfobrings theIANA time zone database (also known as the Olsondatabase) to Python, and its usage is recommended.
- IANA 時區資料庫
The Time Zone Database (often called tz, tzdata or zoneinfo) contains codeand data that represent the history of local time for many representativelocations around the globe. It is updated periodically to reflect changesmade by political bodies to time zone boundaries, UTC offsets, anddaylight-saving rules.
timezone 物件¶
Thetimezone class is a subclass oftzinfo, eachinstance of which represents a time zone defined by a fixed offset fromUTC.
Objects of this class cannot be used to represent time zone information in thelocations where different offsets are used in different days of the year orwhere historical changes have been made to civil time.
- classdatetime.timezone(offset,name=None)¶
Theoffset argument must be specified as a
timedeltaobject representing the difference between the local time and UTC. It mustbe strictly between-timedelta(hours=24)andtimedelta(hours=24), otherwiseValueErroris raised.Thename argument is optional. If specified it must be a string thatwill be used as the value returned by the
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
timezoneinstance isconstructed.Thedt argument is ignored. The return value is a
timedeltainstance 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
timezoneinstanceis constructed.Ifname is not provided in the constructor, the name returned by
tzname(dt)is generated from the value of theoffsetas follows. Ifoffset istimedelta(0), the name is "UTC", otherwise it is a string inthe formatUTC±HH:MM, where ± is the sign ofoffset, HH and MM aretwo digits ofoffset.hoursandoffset.minutesrespectively.在 3.6 版的變更:Name generated from
offset=timedelta(0)is now plain'UTC', not'UTC+00:00'.
- timezone.dst(dt)¶
總是回傳
None。
- timezone.fromutc(dt)¶
Return
dt+offset. Thedt argument must be an awaredatetimeinstance, withtzinfoset toself.
類別屬性:
- timezone.utc¶
UTC 時區,
timezone(timedelta(0))。
strftime() 與strptime() 的行為¶
date,datetime, andtime objects all support astrftime(format) method, to create a string representing the time under thecontrol of an explicit format string.
Conversely, thedate.strptime(),datetime.strptime() andtime.strptime() class methods create an object from a stringrepresenting the time and a corresponding format string.
The table below provides a high-level comparison ofstrftime()versusstrptime():
|
| |
|---|---|---|
用法 | Convert object to a string according to a given format | Parse a string into an object given a corresponding format |
Type of method | 實例方法 | 類別方法 |
Signature |
|
|
strftime() 與strptime() 格式碼¶
These methods accept format codes that can be used to parse and format dates:
>>>datetime.strptime('31/01/22 23:59:59.999999',...'%d/%m/%y %H:%M:%S.%f')datetime.datetime(2022, 1, 31, 23, 59, 59, 999999)>>>_.strftime('%a%d %b %Y, %I:%M%p')'Mon 31 Jan 2022, 11:59PM'
The following is a list of all the format codes that the 1989 C standardrequires, and these work on all platforms with a standard C implementation.
Directive | 含義 | 範例 | 註解 |
|---|---|---|---|
| Weekday as locale'sabbreviated name. | Sun, Mon, ..., Sat(en_US); So, Mo, ..., Sa(de_DE) | (1) |
| Weekday as locale's full name. | Sunday, Monday, ...,Saturday (en_US); Sonntag, Montag, ...,Samstag (de_DE) | (1) |
| Weekday as a decimal number,where 0 is Sunday and 6 isSaturday. | 0, 1, ..., 6 | |
| Day of the month as azero-padded decimal number. | 01, 02, ..., 31 | (9) |
| Month as locale's abbreviatedname. | Jan, Feb, ..., Dec(en_US); Jan, Feb, ..., Dez(de_DE) | (1) |
| Month as locale's full name. | January, February,..., December (en_US); Januar, Februar, ...,Dezember (de_DE) | (1) |
| 以零填充的並以十進位數字表示的月份。 | 01, 02, ..., 12 | (9) |
| Year without century as azero-padded decimal number. | 00, 01, ..., 99 | (9) |
| Year with century as a decimalnumber. | 0001, 0002, ..., 2013,2014, ..., 9998, 9999 | (2) |
| Hour (24-hour clock) as azero-padded decimal number. | 00, 01, ..., 23 | (9) |
| Hour (12-hour clock) as azero-padded decimal number. | 01, 02, ..., 12 | (9) |
| Locale's equivalent of eitherAM or PM. | AM, PM (en_US); am, pm (de_DE) | (1),(3) |
| Minute as a zero-paddeddecimal number. | 00, 01, ..., 59 | (9) |
| Second as a zero-paddeddecimal number. | 00, 01, ..., 59 | (4),(9) |
| Microsecond as a decimalnumber, zero-padded to 6digits. | 000000, 000001, ...,999999 | (5) |
| UTC offset in the form | (empty), +0000,-0400, +1030,+063415,-030712.345216 | (6) |
| Time zone name (empty stringif the object is naive). | (empty), UTC, GMT | (6) |
| Day of the year as azero-padded decimal number. | 001, 002, ..., 366 | (9) |
| Week number of the year(Sunday as the first day ofthe week) as a zero-paddeddecimal number. All days in anew year preceding the firstSunday are considered to be inweek 0. | 00, 01, ..., 53 | (7),(9) |
| Week number of the year(Monday as the first day ofthe week) as a zero-paddeddecimal number. All days in anew year preceding the firstMonday are considered to be inweek 0. | 00, 01, ..., 53 | (7),(9) |
| Locale's appropriate date andtime representation. | Tue Aug 16 21:30:001988 (en_US); Di 16 Aug 21:30:001988 (de_DE) | (1) |
| Locale's appropriate daterepresentation. | 08/16/88 (None); 08/16/1988 (en_US); 16.08.1988 (de_DE) | (1) |
| Locale's appropriate timerepresentation. | 21:30:00 (en_US); 21:30:00 (de_DE) | (1) |
| A literal | % |
Several additional directives not required by the C89 standard are included forconvenience. These parameters all correspond to ISO 8601 date values.
Directive | 含義 | 範例 | 註解 |
|---|---|---|---|
| ISO 8601 year with centuryrepresenting the year thatcontains the greater part ofthe ISO week ( | 0001, 0002, ..., 2013,2014, ..., 9998, 9999 | (8) |
| ISO 8601 weekday as a decimalnumber where 1 is Monday. | 1, 2, ..., 7 | |
| ISO 8601 week as a decimalnumber with Monday asthe first day of the week.Week 01 is the week containingJan 4. | 01, 02, ..., 53 | (8),(9) |
| UTC offset in the form | (empty), +00:00,-04:00, +10:30,+06:34:15,-03:07:12.345216 | (6) |
These may not be available on all platforms when used with thestrftime()method. The ISO 8601 year and ISO 8601 week directives are not interchangeablewith the year and week number directives above. Callingstrptime() withincomplete or ambiguous ISO 8601 directives will raise aValueError.
The full set of format codes supported varies across platforms, because Pythoncalls the platform C library'sstrftime() function, and platformvariations are common. To see the full set of format codes supported on yourplatform, consult thestrftime(3) documentation. There are alsodifferences between platforms in handling of unsupported format specifiers.
在 3.6 版被加入:新增%G、%u 與%V。
在 3.12 版被加入:新增%:z。
技術細節¶
Broadly speaking,d.strftime(fmt) acts like thetime module'stime.strftime(fmt,d.timetuple()) although not all objects support atimetuple() method.
For thedatetime.strptime() class method, the default value is1900-01-01T00:00:00.000: any components not specified in the format stringwill be pulled from the default value.[4]
Usingdatetime.strptime(date_string,format) is equivalent to:
datetime(*(time.strptime(date_string,format)[0:6]))
except when the format includes sub-second components or time zone offsetinformation, which are supported indatetime.strptime but are discarded bytime.strptime.
對time 物件來說,不應該使用年、月、日的格式碼,因為time 物件並沒有這些值。如果使用這些格式碼,年份會以 1900 代替、月及日會以 1 代替。
對date 物件來說,不應該使用時、分、秒、微秒的格式碼,因為date 物件並沒有這些值。如果使用這些格式碼,這些值都會以 0 代替。
For the same reason, handling of format strings containing Unicode code pointsthat can't be represented in the charset of the current locale is alsoplatform-dependent. On some platforms such code points are preserved intact inthe output, while on othersstrftime may raiseUnicodeError or returnan empty string instead.
註解:
Because the format depends on the current locale, care should be taken whenmaking assumptions about the output value. Field orderings will vary (forexample, "month/day/year" versus "day/month/year"), and the output maycontain non-ASCII characters.
The
strptime()method can parse years in the full [1, 9999] range, butyears < 1000 must be zero-filled to 4-digit width.在 3.2 版的變更:In previous versions,
strftime()method was restricted toyears >= 1900.在 3.3 版的變更:In version 3.2,
strftime()method was restricted toyears >= 1000.When used with the
strptime()method, the%pdirective only affectsthe output hour field if the%Idirective is used to parse the hour.Unlike the
timemodule, thedatetimemodule does not supportleap seconds.When used with the
strptime()method, the%fdirectiveaccepts from one to six digits and zero pads on the right.%fisan extension to the set of format characters in the C standard (butimplemented separately in datetime objects, and therefore alwaysavailable).For a naive object, the
%z,%:zand%Zformat codes are replacedby empty strings.For an aware object:
%zutcoffset()is transformed into a string of the form±HHMM[SS[.ffffff]], whereHHis a 2-digit string giving the numberof UTC offset hours,MMis a 2-digit string giving the number of UTCoffset minutes,SSis a 2-digit string giving the number of UTC offsetseconds andffffffis a 6-digit string giving the number of UTCoffset microseconds. Theffffffpart is omitted when the offset is awhole number of seconds and both theffffffand theSSpart isomitted when the offset is a whole number of minutes. For example, ifutcoffset()returnstimedelta(hours=-3,minutes=-30),%zisreplaced with the string'-0330'.
在 3.7 版的變更:The UTC offset is not restricted to a whole number of minutes.
在 3.7 版的變更:When the
%zdirective is provided to thestrptime()method,the UTC offsets can have a colon as a separator between hours, minutesand seconds.For example,'+01:00:00'will be parsed as an offset of one hour.In addition, providing'Z'is identical to'+00:00'.%:zBehaves exactly as
%z, but has a colon separator added betweenhours, minutes and seconds.%ZIn
strftime(),%Zis replaced by an empty string iftzname()returnsNone; otherwise%Zis replaced by thereturned value, which must be a string.strptime()only accepts certain values for%Z:any value in
time.tznamefor your machine's localethe hard-coded values
UTCandGMT
So someone living in Japan may have
JST,UTC, andGMTasvalid values, but probably notEST. It will raiseValueErrorforinvalid values.
在 3.2 版的變更:When the
%zdirective is provided to thestrptime()method, anawaredatetimeobject will be produced. Thetzinfoof theresult will be set to atimezoneinstance.When used with the
strptime()method,%Uand%Ware only usedin calculations when the day of the week and the calendar year (%Y)are specified.Similar to
%Uand%W,%Vis only used in calculations when theday of the week and the ISO year (%G) are specified in astrptime()format string. Also note that%Gand%Yare notinterchangeable.When used with the
strptime()method, the leading zero is optionalfor formats%d,%m,%H,%I,%M,%S,%j,%U,%W, and%V. Format%ydoes require a leading zero.When parsing a month and day using
strptime(), alwaysinclude a year in the format. If the value you need to parse lacks a year,append an explicit dummy leap year. Otherwise your code will raise anexception when it encounters leap day because the default year used by theparser is not a leap year. Users run into this bug every four years...>>>month_day="02/29">>>datetime.strptime(f"{month_day};1984","%m/%d;%Y")# 沒有閏年問題。datetime.datetime(1984, 2, 29, 0, 0)
Deprecated since version 3.13, will be removed in version 3.15:
strptime()calls using a format string containinga day of month without a year now emit aDeprecationWarning. In 3.15 or later we may change this intoan error or change the default year to a leap year. Seegh-70647.
註解
[1]也就是說,我們會忽略相對論的效應
[2]This matches the definition of the "proleptic Gregorian" calendar inDershowitz and Reingold's bookCalendrical Calculations,where it's the base calendar for all computations. See the book foralgorithms for converting between proleptic Gregorian ordinals andmany other calendar systems.
[3]See R. H. van Gent'sguide to the mathematics of the ISO 8601 calendarfor a good explanation.
[4]Passingdatetime.strptime('Feb29','%b%d') will fail since 1900 is not a leap year.