15.3. time — Time access and conversions¶
This module provides various time-related functions. For related
functionality, see also the datetime and calendar modules.
Although this module is always available, not all functions are available on all platforms. Most of the functions defined in this module call platform C library functions with the same name. It may sometimes be helpful to consult the platform documentation, because the semantics of these functions varies among platforms.
An explanation of some terminology and conventions is in order.
The epoch is the point where the time starts. On January 1st of that year, at 0 hours, the “time since the epoch” is zero. For Unix, the epoch is 1970. To find out what the epoch is, look at
gmtime(0).
The functions in this module do not handle dates and times before the epoch or far in the future. The cut-off point in the future is determined by the C library; for Unix, it is typically in 2038.
Year 2000 (Y2K) issues: Python depends on the platform’s C library, which generally doesn’t have year 2000 issues, since all dates and times are represented internally as seconds since the epoch. Functions accepting a
struct_time(see below) generally require a 4-digit year. For backward compatibility, 2-digit years are supported if the module variableaccept2dyearis a non-zero integer; this variable is initialized to1unless the environment variablePYTHONY2Kis set to a non-empty string, in which case it is initialized to0. Thus, you can setPYTHONY2Kto a non-empty string in the environment to require 4-digit years for all year input. When 2-digit years are accepted, they are converted according to the POSIX or X/Open standard: values 69-99 are mapped to 1969-1999, and values 0–68 are mapped to 2000–2068. Values 100–1899 are always illegal.
UTC is Coordinated Universal Time (formerly known as Greenwich Mean Time, or GMT). The acronym UTC is not a mistake but a compromise between English and French.
DST is Daylight Saving Time, an adjustment of the timezone by (usually) one hour during part of the year. DST rules are magic (determined by local law) and can change from year to year. The C library has a table containing the local rules (often it is read from a system file for flexibility) and is the only source of True Wisdom in this respect.
The precision of the various real-time functions may be less than suggested by the units in which their value or argument is expressed. E.g. on most Unix systems, the clock “ticks” only 50 or 100 times a second.
On the other hand, the precision of
time()andsleep()is better than their Unix equivalents: times are expressed as floating point numbers,time()returns the most accurate time available (using Unixgettimeofday()where available), andsleep()will accept a time with a nonzero fraction (Unixselect()is used to implement this, where available).The time value as returned by
gmtime(),localtime(), andstrptime(), and accepted byasctime(),mktime()andstrftime(), may be considered as a sequence of 9 integers. The return values ofgmtime(),localtime(), andstrptime()also offer attribute names for individual fields.See
struct_timefor a description of these objects.Changed in version 2.2: The time value sequence was changed from a tuple to a
struct_time, with the addition of attribute names for the fields.Use the following functions to convert between time representations:
From
To
Use
seconds since the epoch
struct_timein UTCseconds since the epoch
struct_timein local timestruct_timein UTCseconds since the epoch
struct_timein local timeseconds since the epoch
The module defines the following functions and data items:
-
time.accept2dyear¶ Boolean value indicating whether two-digit year values will be accepted. This is true by default, but will be set to false if the environment variable
PYTHONY2Khas been set to a non-empty string. It may also be modified at run time.
-
time.altzone¶ The offset of the local DST timezone, in seconds west of UTC, if one is defined. This is negative if the local DST timezone is east of UTC (as in Western Europe, including the UK). Only use this if
daylightis nonzero.
-
time.asctime([t])¶ Convert a tuple or
struct_timerepresenting a time as returned bygmtime()orlocaltime()to a 24-character string of the following form:'Sun Jun 20 23:21:05 1993'. If t is not provided, the current time as returned bylocaltime()is used. Locale information is not used byasctime().Note
Unlike the C function of the same name, there is no trailing newline.
Changed in version 2.1: Allowed t to be omitted.
-
time.clock()¶ On Unix, return the current processor time as a floating point number expressed in seconds. The precision, and in fact the very definition of the meaning of “processor time”, depends on that of the C function of the same name, but in any case, this is the function to use for benchmarking Python or timing algorithms.
On Windows, this function returns wall-clock seconds elapsed since the first call to this function, as a floating point number, based on the Win32 function
QueryPerformanceCounter(). The resolution is typically better than one microsecond.
-
time.ctime([secs])¶ Convert a time expressed in seconds since the epoch to a string representing local time. If secs is not provided or
None, the current time as returned bytime()is used.ctime(secs)is equivalent toasctime(localtime(secs)). Locale information is not used byctime().Changed in version 2.1: Allowed secs to be omitted.
Changed in version 2.4: If secs is
None, the current time is used.
-
time.daylight¶ Nonzero if a DST timezone is defined.
-
time.gmtime([secs])¶ Convert a time expressed in seconds since the epoch to a
struct_timein UTC in which the dst flag is always zero. If secs is not provided orNone, the current time as returned bytime()is used. Fractions of a second are ignored. See above for a description of thestruct_timeobject. Seecalendar.timegm()for the inverse of this function.Changed in version 2.1: Allowed secs to be omitted.
Changed in version 2.4: If secs is
None, the current time is used.
-
time.localtime([secs])¶ Like
gmtime()but converts to local time. If secs is not provided orNone, the current time as returned bytime()is used. The dst flag is set to1when DST applies to the given time.Changed in version 2.1: Allowed secs to be omitted.
Changed in version 2.4: If secs is
None, the current time is used.
-
time.mktime(t)¶ This is the inverse function of
localtime(). Its argument is thestruct_timeor full 9-tuple (since the dst flag is needed; use-1as the dst flag if it is unknown) which expresses the time in local time, not UTC. It returns a floating point number, for compatibility withtime(). If the input value cannot be represented as a valid time, eitherOverflowErrororValueErrorwill be raised (which depends on whether the invalid value is caught by Python or the underlying C libraries). The earliest date for which it can generate a time is platform-dependent.
-
time.sleep(secs)¶ Suspend execution of the current thread for the given number of seconds. The argument may be a floating point number to indicate a more precise sleep time. The actual suspension time may be less than that requested because any caught signal will terminate the
sleep()following execution of that signal’s catching routine. Also, the suspension time may be longer than requested by an arbitrary amount because of the scheduling of other activity in the system.
-
time.strftime(format[, t])¶ Convert a tuple or
struct_timerepresenting a time as returned bygmtime()orlocaltime()to a string as specified by the format argument. If t is not provided, the current time as returned bylocaltime()is used. format must be a string.ValueErroris raised if any field in t is outside of the allowed range.strftime()returns a locale dependent byte string; the result may be converted to unicode by doingstrftime(<myformat>).decode(locale.getlocale()[1]).Changed in version 2.1: Allowed t to be omitted.
Changed in version 2.4:
ValueErrorraised if a field in t is out of range.Changed in version 2.5: 0 is now a legal argument for any position in the time tuple; if it is normally illegal the value is forced to a correct one.
The following directives can be embedded in the format string. They are shown without the optional field width and precision specification, and are replaced by the indicated characters in the
strftime()result:Directive
Meaning
Notes
%aLocale’s abbreviated weekday name.
%ALocale’s full weekday name.
%bLocale’s abbreviated month name.
%BLocale’s full month name.
%cLocale’s appropriate date and time representation.
%dDay of the month as a decimal number [01,31].
%HHour (24-hour clock) as a decimal number [00,23].
%IHour (12-hour clock) as a decimal number [01,12].
%jDay of the year as a decimal number [001,366].
%mMonth as a decimal number [01,12].
%MMinute as a decimal number [00,59].
%pLocale’s equivalent of either AM or PM.
(1)
%SSecond as a decimal number [00,61].
(2)
%UWeek number of the year (Sunday as the first day of the week) as a decimal number [00,53]. All days in a new year preceding the first Sunday are considered to be in week 0.
(3)
%wWeekday as a decimal number [0(Sunday),6].
%WWeek number of the year (Monday as the first day of the week) as a decimal number [00,53]. All days in a new year preceding the first Monday are considered to be in week 0.
(3)
%xLocale’s appropriate date representation.
%XLocale’s appropriate time representation.
%yYear without century as a decimal number [00,99].
%YYear with century as a decimal number.
%ZTime zone name (no characters if no time zone exists).
%%A literal
'%'character.Notes:
When used with the
strptime()function, the%pdirective only affects the output hour field if the%Idirective is used to parse the hour.The range really is
0to61; this accounts for leap seconds and the (very rare) double leap seconds.When used with the
strptime()function,%Uand%Ware only used in calculations when the day of the week and the year are specified.
Here is an example, a format for dates compatible with that specified in the RFC 2822 Internet email standard. 1
>>> from time import gmtime, strftime >>> strftime("%a, %d %b %Y %H:%M:%S +0000", gmtime()) 'Thu, 28 Jun 2001 14:17:15 +0000'
Additional directives may be supported on certain platforms, but only the ones listed here have a meaning standardized by ANSI C. To see the full set of format codes supported on your platform, consult the strftime(3) documentation.
On some platforms, an optional field width and precision specification can immediately follow the initial
'%'of a directive in the following order; this is also not portable. The field width is normally 2 except for%jwhere it is 3.
-
time.strptime(string[, format])¶ Parse a string representing a time according to a format. The return value is a
struct_timeas returned bygmtime()orlocaltime().The format parameter uses the same directives as those used by
strftime(); it defaults to"%a %b %d %H:%M:%S %Y"which matches the formatting returned byctime(). If string cannot be parsed according to format, or if it has excess data after parsing,ValueErroris raised. The default values used to fill in any missing data when more accurate values cannot be inferred are(1900, 1, 1, 0, 0, 0, 0, 1, -1).For example:
>>> import time >>> time.strptime("30 Nov 00", "%d %b %y") time.struct_time(tm_year=2000, tm_mon=11, tm_mday=30, tm_hour=0, tm_min=0, tm_sec=0, tm_wday=3, tm_yday=335, tm_isdst=-1)
Support for the
%Zdirective is based on the values contained intznameand whetherdaylightis true. Because of this, it is platform-specific except for recognizing UTC and GMT which are always known (and are considered to be non-daylight savings timezones).Only the directives specified in the documentation are supported. Because
strftime()is implemented per platform it can sometimes offer more directives than those listed. Butstrptime()is independent of any platform and thus does not necessarily support all directives available that are not documented as supported.
-
class
time.struct_time¶ The type of the time value sequence returned by
gmtime(),localtime(), andstrptime(). It is an object with a named tuple interface: values can be accessed by index and by attribute name. The following values are present:Index
Attribute
Values
0
tm_year(for example, 1993)
1
tm_monrange [1, 12]
2
tm_mdayrange [1, 31]
3
tm_hourrange [0, 23]
4
tm_minrange [0, 59]
5
tm_secrange [0, 61]; see (2) in
strftime()description6
tm_wday
