<!DOCTYPE html PUBLIC
"-//W3C//DTD HTML 4.0 Transitional//EN">
<link rel=
"STYLESHEET" href=
"lib.css" type='text/css'
/>
<link rel=
"SHORTCUT ICON" href=
"../icons/pyfav.png" type=
"image/png" />
<link rel='start' href='../index.html' title='Python Documentation Index'
/>
<link rel=
"first" href=
"lib.html" title='Python Library Reference'
/>
<link rel='contents' href='contents.html'
title=
"Contents" />
<link rel='index' href='genindex.html' title='Index'
/>
<link rel='last' href='about.html' title='About this document...'
/>
<link rel='help' href='about.html' title='About this document...'
/>
<link rel=
"next" href=
"module-sched.html" />
<link rel=
"prev" href=
"module-datetime.html" />
<link rel=
"parent" href=
"allos.html" />
<link rel=
"next" href=
"module-sched.html" />
<meta name='aesop' content='information'
/>
<title>6.11 time -- Time access and conversions
</title>
<div id='top-navigation-panel' xml:id='top-navigation-panel'
>
<table align=
"center" width=
"100%" cellpadding=
"0" cellspacing=
"2">
<td class='online-navigation'
><a rel=
"prev" title=
"6.10.7 strftime() Behavior"
href=
"node257.html"><img src='../icons/previous.png'
border='
0' height='
32' alt='Previous Page' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"parent" title=
"6. Generic Operating System"
href=
"allos.html"><img src='../icons/up.png'
border='
0' height='
32' alt='Up One Level' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"next" title=
"6.12 sched "
href=
"module-sched.html"><img src='../icons/next.png'
border='
0' height='
32' alt='Next Page' width='
32'
/></A></td><td align=
"center" width=
"100%">Python Library Reference
</td>
<td class='online-navigation'
><a rel=
"contents" title=
"Table of Contents"
href=
"contents.html"><img src='../icons/contents.png'
border='
0' height='
32' alt='Contents' width='
32'
/></A></td><td class='online-navigation'
><a href=
"modindex.html" title=
"Module Index"><img src='../icons/modules.png'
border='
0' height='
32' alt='Module Index' width='
32'
/></a></td><td class='online-navigation'
><a rel=
"index" title=
"Index"
href=
"genindex.html"><img src='../icons/index.png'
border='
0' height='
32' alt='Index' width='
32'
/></A></td><div class='online-navigation'
>
<b class=
"navlabel">Previous:
</b>
<a class=
"sectref" rel=
"prev" href=
"node257.html">6.10.7 strftime() Behavior
</A>
<b class=
"navlabel">Up:
</b>
<a class=
"sectref" rel=
"parent" href=
"allos.html">6. Generic Operating System
</A>
<b class=
"navlabel">Next:
</b>
<a class=
"sectref" rel=
"next" href=
"module-sched.html">6.12 sched
</A>
<!--End of Navigation Panel-->
<H1><A NAME=
"SECTION0081100000000000000000">
6.11 <tt class=
"module">time
</tt> --
Time access and conversions
</A><A NAME=
"module-time"></A>
This module provides various time-related functions. It is always
available, but 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
An explanation of some terminology and conventions is in order.
<LI>The
<i class=
"dfn">epoch
</i><a id='l2h-
1962' xml:id='l2h-
1962'
></a> is the point where the time starts. On
January
1st of that year, at
0 hours, the ``time since the epoch'' is
zero. For
<span class=
"Unix">Unix
</span>, the epoch is
1970. To find out what the epoch is,
look at
<code>gmtime(
0)
</code>.
<LI>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
<span class=
"Unix">Unix
</span>, it is typically in
2038<a id='l2h-
1963' xml:id='l2h-
1963'
></a>.
<LI><strong>Year
2000 (Y2K) issues
</strong>:
<a id='l2h-
1964' xml:id='l2h-
1964'
></a> 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
<tt class=
"class">struct_time
</tt>(see below) generally require a
4-digit year. For backward
compatibility,
2-digit years are supported if the module variable
<code>accept2dyear
</code> is a non-zero integer; this variable is
initialized to
<code>1</code> unless the environment variable
<a class=
"envvar" id='l2h-
1965' xml:id='l2h-
1965'
>PYTHONY2K
</a> is set to a non-empty string, in which case it is
initialized to
<code>0</code>. Thus, you can set
<a class=
"envvar" id='l2h-
1966' xml:id='l2h-
1966'
>PYTHONY2K
</a> to 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-
99are mapped to
1969-
1999, and values
0-
68 are mapped to
2000-
2068.
Values
100-
1899 are always illegal. Note that this is new as of
Python
1.5.2(a2); earlier versions, up to Python
1.5.1 and
1.5.2a1,
would add
1900 to year values below
1900.
<LI>UTC
<a id='l2h-
1967' xml:id='l2h-
1967'
></a> is Coordinated Universal Time
<a id='l2h-
1968' xml:id='l2h-
1968'
></a> (formerly known as Greenwich Mean
Time,
<a id='l2h-
1969' xml:id='l2h-
1969'
></a> or GMT). The acronym UTC is not a
mistake but a compromise between English and French.
<LI>DST is Daylight Saving Time,
<a id='l2h-
1970' xml:id='l2h-
1970'
></a> 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.
<LI>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
<span class=
"Unix">Unix
</span> systems, the clock ``ticks'' only
50 or
100 times a
second, and on the Mac, times are only accurate to whole seconds.
<LI>On the other hand, the precision of
<tt class=
"function">time()
</tt> and
<tt class=
"function">sleep()
</tt> is better than their
<span class=
"Unix">Unix
</span> equivalents: times are
expressed as floating point numbers,
<tt class=
"function">time()
</tt> returns the
most accurate time available (using
<span class=
"Unix">Unix
</span> <tt class=
"cfunction">gettimeofday()
</tt>where available), and
<tt class=
"function">sleep()
</tt> will accept a time with a
nonzero fraction (
<span class=
"Unix">Unix
</span> <tt class=
"cfunction">select()
</tt> is used to implement
<LI>The time value as returned by
<tt class=
"function">gmtime()
</tt>,
<tt class=
"function">localtime()
</tt>, and
<tt class=
"function">strptime()
</tt>, and accepted by
<tt class=
"function">asctime()
</tt>,
<tt class=
"function">mktime()
</tt> and
<tt class=
"function">strftime()
</tt>,
is a sequence of
9 integers. The return values of
<tt class=
"function">gmtime()
</tt>,
<tt class=
"function">localtime()
</tt>, and
<tt class=
"function">strptime()
</tt> also offer attribute
names for individual fields.
<div class=
"center"><table class=
"realtable">
<th class=
"center">Index
</th>
<th class=
"left" >Attribute
</th>
<th class=
"left" >Values
</th>
<tr><td class=
"center" valign=
"baseline"><code>0</code></td>
<td class=
"left" ><tt class=
"member">tm_year
</tt></td>
<td class=
"left" >(for example,
1993)
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>1</code></td>
<td class=
"left" ><tt class=
"member">tm_mon
</tt></td>
<td class=
"left" >range [
1,
12]
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>2</code></td>
<td class=
"left" ><tt class=
"member">tm_mday
</tt></td>
<td class=
"left" >range [
1,
31]
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>3</code></td>
<td class=
"left" ><tt class=
"member">tm_hour
</tt></td>
<td class=
"left" >range [
0,
23]
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>4</code></td>
<td class=
"left" ><tt class=
"member">tm_min
</tt></td>
<td class=
"left" >range [
0,
59]
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>5</code></td>
<td class=
"left" ><tt class=
"member">tm_sec
</tt></td>
<td class=
"left" >range [
0,
61]; see
<strong>(
1)
</strong> in
<tt class=
"function">strftime()
</tt> description
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>6</code></td>
<td class=
"left" ><tt class=
"member">tm_wday
</tt></td>
<td class=
"left" >range [
0,
6], Monday is
0</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>7</code></td>
<td class=
"left" ><tt class=
"member">tm_yday
</tt></td>
<td class=
"left" >range [
1,
366]
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>8</code></td>
<td class=
"left" ><tt class=
"member">tm_isdst
</tt></td>
<td class=
"left" >0,
1 or -
1; see below
</td></tr></tbody>
Note that unlike the C structure, the month value is a
range of
1-
12, not
0-
11. A year value will be handled as described
under ``Year
2000 (Y2K) issues'' above. A
<code>-
1</code> argument as the
daylight savings flag, passed to
<tt class=
"function">mktime()
</tt> will usually
result in the correct daylight savings state to be filled in.
When a tuple with an incorrect length is passed to a function
expecting a
<tt class=
"class">struct_time
</tt>, or having elements of the wrong type, a
<tt class=
"exception">TypeError
</tt> is raised.
<span class=
"versionnote">Changed in version
2.2:
The time value sequence was changed from a tuple to a
<tt class=
"class">struct_time
</tt>, with the addition of attribute names
The module defines the following functions and data items:
<dl><dt><b><tt id='l2h-
1945' xml:id='l2h-
1945'
>accept2dyear
</tt></b></dt>
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
<a class=
"envvar" id='l2h-
1971' xml:id='l2h-
1971'
>PYTHONY2K
</a> has been set to a non-empty
string. It may also be modified at run time.
<dl><dt><b><tt id='l2h-
1946' xml:id='l2h-
1946'
>altzone
</tt></b></dt>
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
<code>daylight
</code> is nonzero.
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1947' xml:id='l2h-
1947'
class=
"function">asctime
</tt></b>(
</nobr></td>
<td><var></var><big>[
</big><var>t
</var><big>]
</big><var></var>)
</td></tr></table></dt>
Convert a tuple or
<tt class=
"class">struct_time
</tt> representing a time as returned
by
<tt class=
"function">gmtime()
</tt>or
<tt class=
"function">localtime()
</tt> to a
24-character string of the following form:
<code>'Sun Jun
20 23:
21:
05 1993'
</code>. If
<var>t
</var> is not provided, the
current time as returned by
<tt class=
"function">localtime()
</tt> is used.
Locale information is not used by
<tt class=
"function">asctime()
</tt>.
<span class=
"note"><b class=
"label">Note:
</b>
Unlike the C function of the same name, there is no trailing
<span class=
"versionnote">Changed in version
2.1:
Allowed
<var>t
</var> to be omitted.
</span><dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1948' xml:id='l2h-
1948'
class=
"function">clock
</tt></b>(
</nobr></td>
<td><var></var>)
</td></tr></table></dt>
On
<span class=
"Unix">Unix
</span>, 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''
<a id='l2h-
1972' xml:id='l2h-
1972'
></a>, depends
on that of the C function of the same name, but in any case, this is
the function to use for benchmarking
<a id='l2h-
1973' xml:id='l2h-
1973'
></a> Python or
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
<tt class=
"cfunction">QueryPerformanceCounter()
</tt>.
The resolution is typically better than one microsecond.
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1949' xml:id='l2h-
1949'
class=
"function">ctime
</tt></b>(
</nobr></td>
<td><var></var><big>[
</big><var>secs
</var><big>]
</big><var></var>)
</td></tr></table></dt>
Convert a time expressed in seconds since the epoch to a string
representing local time. If
<var>secs
</var> is not provided or
<tt class=
"constant">None
</tt>, the current time as returned by
<tt class=
"function">time()
</tt> is
used.
<code>ctime(
<var>secs
</var>)
</code> is equivalent to
<code>asctime(localtime(
<var>secs
</var>))
</code>.
Locale information is not used by
<tt class=
"function">ctime()
</tt>.
<span class=
"versionnote">Changed in version
2.1:
Allowed
<var>secs
</var> to be omitted.
</span><span class=
"versionnote">Changed in version
2.4:
If
<var>secs
</var> is
<tt class=
"constant">None
</tt>, the current time is
<dl><dt><b><tt id='l2h-
1950' xml:id='l2h-
1950'
>daylight
</tt></b></dt>
Nonzero if a DST timezone is defined.
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1951' xml:id='l2h-
1951'
class=
"function">gmtime
</tt></b>(
</nobr></td>
<td><var></var><big>[
</big><var>secs
</var><big>]
</big><var></var>)
</td></tr></table></dt>
Convert a time expressed in seconds since the epoch to a
<tt class=
"class">struct_time
</tt>in UTC in which the dst flag is always zero. If
<var>secs
</var> is not
provided or
<tt class=
"constant">None
</tt>, the current time as returned by
<tt class=
"function">time()
</tt> is used. Fractions of a second are ignored. See
above for a description of the
<tt class=
"class">struct_time
</tt> object. See
<tt class=
"function">calendar.timegm()
</tt> for the inverse of this function.
<span class=
"versionnote">Changed in version
2.1:
Allowed
<var>secs
</var> to be omitted.
</span><span class=
"versionnote">Changed in version
2.4:
If
<var>secs
</var> is
<tt class=
"constant">None
</tt>, the current time is
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1952' xml:id='l2h-
1952'
class=
"function">localtime
</tt></b>(
</nobr></td>
<td><var></var><big>[
</big><var>secs
</var><big>]
</big><var></var>)
</td></tr></table></dt>
Like
<tt class=
"function">gmtime()
</tt> but converts to local time. If
<var>secs
</var> is
not provided or
<tt class=
"constant">None
</tt>, the current time as returned by
<tt class=
"function">time()
</tt> is used. The dst flag is set to
<code>1</code> when DST
applies to the given time.
<span class=
"versionnote">Changed in version
2.1:
Allowed
<var>secs
</var> to be omitted.
</span><span class=
"versionnote">Changed in version
2.4:
If
<var>secs
</var> is
<tt class=
"constant">None
</tt>, the current time is
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1953' xml:id='l2h-
1953'
class=
"function">mktime
</tt></b>(
</nobr></td>
<td><var>t
</var>)
</td></tr></table></dt>
This is the inverse function of
<tt class=
"function">localtime()
</tt>. Its argument
is the
<tt class=
"class">struct_time
</tt> or full
9-tuple (since the dst flag is
needed; use
<code>-
1</code> as the dst flag if it is unknown) which
<em>local
</em> time, not UTC. It returns a floating point number, for
compatibility with
<tt class=
"function">time()
</tt>. If the input value cannot be
represented as a valid time, either
<tt class=
"exception">OverflowError
</tt> or
<tt class=
"exception">ValueError
</tt> will 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.
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1954' xml:id='l2h-
1954'
class=
"function">sleep
</tt></b>(
</nobr></td>
<td><var>secs
</var>)
</td></tr></table></dt>
Suspend execution 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
<tt class=
"function">sleep()
</tt> 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.
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1955' xml:id='l2h-
1955'
class=
"function">strftime
</tt></b>(
</nobr></td>
<td><var>format
</var><big>[
</big><var>, t
</var><big>]
</big><var></var>)
</td></tr></table></dt>
Convert a tuple or
<tt class=
"class">struct_time
</tt> representing a time as returned
by
<tt class=
"function">gmtime()
</tt> or
<tt class=
"function">localtime()
</tt> to a string as
specified by the
<var>format
</var> argument. If
<var>t
</var> is not
provided, the current time as returned by
<tt class=
"function">localtime()
</tt> is
used.
<var>format
</var> must be a string.
<tt class=
"exception">ValueError
</tt> is raised
if any field in
<var>t
</var> is outside of the allowed range.
<span class=
"versionnote">Changed in version
2.1:
Allowed
<var>t
</var> to be omitted.
</span><span class=
"versionnote">Changed in version
2.4:
<tt class=
"exception">ValueError
</tt> raised if a field in
<var>t
</var> is
The following directives can be embedded in the
<var>format
</var> string.
They are shown without the optional field width and precision
specification, and are replaced by the indicated characters in the
<tt class=
"function">strftime()
</tt> result:
<div class=
"center"><table class=
"realtable">
<th class=
"center">Directive
</th>
<th class=
"left" >Meaning
</th>
<th class=
"center">Notes
</th>
<tr><td class=
"center" valign=
"baseline"><code>%a
</code></td>
<td class=
"left" >Locale's abbreviated weekday name.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%A
</code></td>
<td class=
"left" >Locale's full weekday name.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%b
</code></td>
<td class=
"left" >Locale's abbreviated month name.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%B
</code></td>
<td class=
"left" >Locale's full month name.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%c
</code></td>
<td class=
"left" >Locale's appropriate date and time representation.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%d
</code></td>
<td class=
"left" >Day of the month as a decimal number [
01,
31].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%H
</code></td>
<td class=
"left" >Hour (
24-hour clock) as a decimal number [
00,
23].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%I
</code></td>
<td class=
"left" >Hour (
12-hour clock) as a decimal number [
01,
12].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%j
</code></td>
<td class=
"left" >Day of the year as a decimal number [
001,
366].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%m
</code></td>
<td class=
"left" >Month as a decimal number [
01,
12].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%M
</code></td>
<td class=
"left" >Minute as a decimal number [
00,
59].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%p
</code></td>
<td class=
"left" >Locale's equivalent of either AM or PM.
</td>
<td class=
"center">(
1)
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%S
</code></td>
<td class=
"left" >Second as a decimal number [
00,
61].
</td>
<td class=
"center">(
2)
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%U
</code></td>
<td class=
"left" >Week 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.
</td> <td class=
"center">(
3)
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%w
</code></td>
<td class=
"left" >Weekday as a decimal number [
0(Sunday),
6].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%W
</code></td>
<td class=
"left" >Week 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.
</td> <td class=
"center">(
3)
</td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%x
</code></td>
<td class=
"left" >Locale's appropriate date representation.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%X
</code></td>
<td class=
"left" >Locale's appropriate time representation.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%y
</code></td>
<td class=
"left" >Year without century as a decimal number [
00,
99].
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%Y
</code></td>
<td class=
"left" >Year with century as a decimal number.
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%Z
</code></td>
<td class=
"left" >Time zone name (no characters if no time zone exists).
</td>
<td class=
"center"></td></tr>
<tr><td class=
"center" valign=
"baseline"><code>%%
</code></td>
<td class=
"left" >A literal
"<tt class="character
">%</tt>" character.
</td>
<td class=
"center"></td></tr></tbody>
<DT><STRONG>(
1)
</STRONG></DT>
<DD>When used with the
<tt class=
"function">strptime()
</tt> function, the
<code>%p
</code>
directive only affects the output hour field if the
<code>%I
</code> directive
is used to parse the hour.
<DT><STRONG>(
2)
</STRONG></DT>
<DD>The range really is
<code>0</code> to
<code>61</code>; this accounts for leap
seconds and the (very rare) double leap seconds.
<DT><STRONG>(
3)
</STRONG></DT>
<DD>When used with the
<tt class=
"function">strptime()
</tt> function,
<code>%U
</code> and
<code>%W
</code>
are only used in calculations when the day of the week and the year are
Here is an example, a format for dates compatible with that specified
in the
<a class=
"rfc" id='rfcref-
88249' xml:id='rfcref-
88249'
href=
"http://www.faqs.org/rfcs/rfc2822.html">RFC
2822</a> Internet email standard.
HREF=
"#foot30076"><SUP>6.1</SUP></A>
<div class=
"verbatim"><pre>
>>> 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.
On some platforms, an optional field width and precision
specification can immediately follow the initial
"<tt class="character
">%</tt>" of a
directive in the following order; this is also not portable.
The field width is normally
2 except for
<code>%j
</code> where it is
3.
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1956' xml:id='l2h-
1956'
class=
"function">strptime
</tt></b>(
</nobr></td>
<td><var>string
</var><big>[
</big><var>, format
</var><big>]
</big><var></var>)
</td></tr></table></dt>
Parse a string representing a time according to a format. The return
value is a
<tt class=
"class">struct_time
</tt> as returned by
<tt class=
"function">gmtime()
</tt> or
<tt class=
"function">localtime()
</tt>. The
<var>format
</var> parameter uses the same
directives as those used by
<tt class=
"function">strftime()
</tt>; it defaults to
<code>"%a %b %d %H:%M:%S %Y"</code> which matches the formatting
returned by
<tt class=
"function">ctime()
</tt>. If
<var>string
</var> cannot be parsed
according to
<var>format
</var>,
<tt class=
"exception">ValueError
</tt> is raised. If the
string to be parsed has excess data after parsing,
<tt class=
"exception">ValueError
</tt> is raised. The default values used to fill in
any missing data are
<code>(
1900,
1,
1,
0,
0,
0,
0,
1, -
1)
</code> .
Support for the
<code>%Z
</code> directive is based on the values contained in
<code>tzname
</code> and whether
<code>daylight
</code> is 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
<dl><dt><b><tt id='l2h-
1957' xml:id='l2h-
1957'
>struct_time
</tt></b></dt>
The type of the time value sequence returned by
<tt class=
"function">gmtime()
</tt>,
<tt class=
"function">localtime()
</tt>, and
<tt class=
"function">strptime()
</tt>.
<span class=
"versionnote">New in version
2.2.
</span>
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1958' xml:id='l2h-
1958'
class=
"function">time
</tt></b>(
</nobr></td>
<td><var></var>)
</td></tr></table></dt>
Return the time as a floating point number expressed in seconds since
the epoch, in UTC. Note that even though the time is always returned
as a floating point number, not all systems provide time with a better
precision than
1 second. While this function normally returns
non-decreasing values, it can return a lower value than a previous
call if the system clock has been set back between the two calls.
<dl><dt><b><tt id='l2h-
1959' xml:id='l2h-
1959'
>timezone
</tt></b></dt>
The offset of the local (non-DST) timezone, in seconds west of UTC
(negative in most of Western Europe, positive in the US, zero in the
<dl><dt><b><tt id='l2h-
1960' xml:id='l2h-
1960'
>tzname
</tt></b></dt>
A tuple of two strings: the first is the name of the local non-DST
timezone, the second is the name of the local DST timezone. If no DST
timezone is defined, the second string should not be used.
<dl><dt><table cellpadding=
"0" cellspacing=
"0"><tr valign=
"baseline">
<td><nobr><b><tt id='l2h-
1961' xml:id='l2h-
1961'
class=
"function">tzset
</tt></b>(
</nobr></td>
<td><var></var>)
</td></tr></table></dt>
Resets the time conversion rules used by the library routines.
The environment variable
<a class=
"envvar" id='l2h-
1974' xml:id='l2h-
1974'
>TZ
</a> specifies how this is done.
<span class=
"versionnote">New in version
2.3.
</span>
Availability:
<span class=
"Unix">Unix
</span>.
<div class=
"note"><b class=
"label">Note:
</b>
Although in many cases, changing the
<a class=
"envvar" id='l2h-
1975' xml:id='l2h-
1975'
>TZ
</a> environment variable
may affect the output of functions like
<tt class=
"function">localtime
</tt> without calling
<tt class=
"function">tzset
</tt>, this behavior should not be relied on.
The
<a class=
"envvar" id='l2h-
1976' xml:id='l2h-
1976'
>TZ
</a> environment variable should contain no whitespace.
The standard format of the
<a class=
"envvar" id='l2h-
1977' xml:id='l2h-
1977'
>TZ
</a> environment variable is:
(whitespace added for clarity)
<DT>std offset [dst [offset] [,start[/time], end[/time]
</DT>
<DD>Three or more alphanumerics giving the timezone abbreviations.
These will be propagated into time.tzname
<DD>The offset has the form:
± hh[:mm[:ss]].
This indicates the value added the local time to arrive at UTC.
If preceded by a '-', the timezone is east of the Prime
Meridian; otherwise, it is west. If no offset follows
dst, summer time is assumed to be one hour ahead of standard time.
<DT>start[/time],end[/time]
</DT>
<DD>Indicates when to change to and back from DST. The format of the
start and end dates are one of the following:
<DD>The Julian day
<var>n
</var> (
1 <=
<var>n
</var> <=
365). Leap days are not
counted, so in all years February
28 is day
59 and
<DD>The zero-based Julian day (
0 <=
<var>n
</var> <=
365). Leap days are
counted, and it is possible to refer to February
29.
<DT>M
<var>m
</var>.
<var>n
</var>.
<var>d
</var></DT>
<DD>The
<var>d
</var>'th day (
0 <=
<var>d
</var> <=
6) or week
<var>n
</var>
of month
<var>m
</var> of the year (
1 <=
<var>n
</var> <=
5,
1 <=
<var>m
</var> <=
12, where week
5 means
"the last <var>d</var> day
in month <var>m</var>" which may occur in either the fourth or
the fifth week). Week
1 is the first week in which the
<var>d
</var>'th day occurs. Day zero is Sunday.
time has the same format as offset except that no leading sign ('-' or
'+') is allowed. The default, if time is not given, is
02:
00:
00.
<div class=
"verbatim"><pre>
>>> os.environ['TZ'] = 'EST+
05EDT,M4.1
.0,M10.5
.0'
>>> time.tzset()
>>> time.strftime('%X %x %Z')
>>> os.environ['TZ'] = 'AEST-
10AEDT-
11,M10.5
.0,M3.5
.0'
>>> time.tzset()
>>> time.strftime('%X %x %Z')
On many Unix systems (including *BSD, Linux, Solaris, and Darwin), it
is more convenient to use the system's zoneinfo (
<span class=
"manpage"><i>tzfile
</i>(
5)
</span>)
database to specify the timezone rules. To do this, set the
<a class=
"envvar" id='l2h-
1978' xml:id='l2h-
1978'
>TZ
</a> environment variable to the path of the required timezone
datafile, relative to the root of the systems 'zoneinfo' timezone database,
usually located at
<span class=
"file">/usr/share/zoneinfo
</span>. For example,
<code>'US/Eastern'
</code>,
<code>'Australia/Melbourne'
</code>,
<code>'Egypt'
</code> or
<code>'Europe/Amsterdam'
</code>.
<div class=
"verbatim"><pre>
>>> os.environ['TZ'] = 'US/Eastern'
>>> time.tzset()
>>> os.environ['TZ'] = 'Egypt'
>>> time.tzset()
<p class=
"heading">See Also:
</p>
<dl compact=
"compact" class=
"seemodule">
<dt>Module
<b><tt class=
"module"><a href=
"module-datetime.html">datetime
</a></tt>:
</b>
<dd>More object-oriented interface to dates and times.
<dl compact=
"compact" class=
"seemodule">
<dt>Module
<b><tt class=
"module"><a href=
"module-locale.html">locale
</a></tt>:
</b>
<dd>Internationalization services. The locale
settings can affect the return values for some of
the functions in the
<tt class=
"module">time
</tt> module.
<dl compact=
"compact" class=
"seemodule">
<dt>Module
<b><tt class=
"module"><a href=
"module-calendar.html">calendar
</a></tt>:
</b>
<dd>General calendar-related functions.
<tt class=
"function">timegm()
</tt> is the inverse of
<tt class=
"function">gmtime()
</tt> from this module.
<BR><HR><H4>Footnotes
</H4>
<DT><A NAME=
"foot30076">... standard.
</A><A
href=
"module-time.html#tex2html35"><SUP>6.1</SUP></A></DT>
<DD>The use of
<code>%Z
</code> is now
deprecated, but the
<code>%z
</code> escape that expands to the preferred
hour/minute offset is not supported by all ANSI C libraries. Also,
a strict reading of the original
1982 <a class=
"rfc" id='rfcref-
88203' xml:id='rfcref-
88203'
href=
"http://www.faqs.org/rfcs/rfc822.html">RFC
822</a> standard calls for
a two-digit year (%y rather than %Y), but practice moved to
4-digit years long before the year
2000. The
4-digit year has
been mandated by
<a class=
"rfc" id='rfcref-
88205' xml:id='rfcref-
88205'
href=
"http://www.faqs.org/rfcs/rfc2822.html">RFC
2822</a>, which obsoletes
<a class=
"rfc" id='rfcref-
88207' xml:id='rfcref-
88207'
href=
"http://www.faqs.org/rfcs/rfc822.html">RFC
822</a>.
<div class='online-navigation'
>
<table align=
"center" width=
"100%" cellpadding=
"0" cellspacing=
"2">
<td class='online-navigation'
><a rel=
"prev" title=
"6.10.7 strftime() Behavior"
href=
"node257.html"><img src='../icons/previous.png'
border='
0' height='
32' alt='Previous Page' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"parent" title=
"6. Generic Operating System"
href=
"allos.html"><img src='../icons/up.png'
border='
0' height='
32' alt='Up One Level' width='
32'
/></A></td><td class='online-navigation'
><a rel=
"next" title=
"6.12 sched "
href=
"module-sched.html"><img src='../icons/next.png'
border='
0' height='
32' alt='Next Page' width='
32'
/></A></td><td align=
"center" width=
"100%">Python Library Reference
</td>
<td class='online-navigation'
><a rel=
"contents" title=
"Table of Contents"
href=
"contents.html"><img src='../icons/contents.png'
border='
0' height='
32' alt='Contents' width='
32'
/></A></td><td class='online-navigation'
><a href=
"modindex.html" title=
"Module Index"><img src='../icons/modules.png'
border='
0' height='
32' alt='Module Index' width='
32'
/></a></td><td class='online-navigation'
><a rel=
"index" title=
"Index"
href=
"genindex.html"><img src='../icons/index.png'
border='
0' height='
32' alt='Index' width='
32'
/></A></td><div class='online-navigation'
>
<b class=
"navlabel">Previous:
</b>
<a class=
"sectref" rel=
"prev" href=
"node257.html">6.10.7 strftime() Behavior
</A>
<b class=
"navlabel">Up:
</b>
<a class=
"sectref" rel=
"parent" href=
"allos.html">6. Generic Operating System
</A>
<b class=
"navlabel">Next:
</b>
<a class=
"sectref" rel=
"next" href=
"module-sched.html">6.12 sched
</A>
<span class=
"release-info">Release
2.4.2, documentation updated on
28 September
2005.
</span>
<!--End of Navigation Panel-->
See
<i><a href=
"about.html">About this document...
</a></i> for information on suggesting changes.
projects / OpenSPARC-T2-SAM / blob