blob: 04ddef9be03f506befdb747442643ed99aa9fe94 [file] [log] [blame]
Georg Brandl8ec7f652007-08-15 14:28:01 +00001
2:mod:`time` --- Time access and conversions
3===========================================
4
5.. module:: time
6 :synopsis: Time access and conversions.
7
8
9This module provides various time-related functions. For related
10functionality, see also the :mod:`datetime` and :mod:`calendar` modules.
11
12Although this module is always available,
13not all functions are available on all platforms. Most of the functions
14defined in this module call platform C library functions with the same name. It
15may sometimes be helpful to consult the platform documentation, because the
16semantics of these functions varies among platforms.
17
18An explanation of some terminology and conventions is in order.
19
Georg Brandl78f11ed2010-11-26 07:34:20 +000020.. index:: single: epoch
Georg Brandl8ec7f652007-08-15 14:28:01 +000021
22* The :dfn:`epoch` is the point where the time starts. On January 1st of that
23 year, at 0 hours, the "time since the epoch" is zero. For Unix, the epoch is
24 1970. To find out what the epoch is, look at ``gmtime(0)``.
25
Georg Brandl78f11ed2010-11-26 07:34:20 +000026.. index:: single: Year 2038
Georg Brandl8ec7f652007-08-15 14:28:01 +000027
28* The functions in this module do not handle dates and times before the epoch or
29 far in the future. The cut-off point in the future is determined by the C
30 library; for Unix, it is typically in 2038.
31
Georg Brandl78f11ed2010-11-26 07:34:20 +000032.. index::
33 single: Year 2000
34 single: Y2K
35
36.. _time-y2kissues:
Georg Brandl8ec7f652007-08-15 14:28:01 +000037
38* **Year 2000 (Y2K) issues**: Python depends on the platform's C library, which
39 generally doesn't have year 2000 issues, since all dates and times are
40 represented internally as seconds since the epoch. Functions accepting a
41 :class:`struct_time` (see below) generally require a 4-digit year. For backward
42 compatibility, 2-digit years are supported if the module variable
43 ``accept2dyear`` is a non-zero integer; this variable is initialized to ``1``
44 unless the environment variable :envvar:`PYTHONY2K` is set to a non-empty
45 string, in which case it is initialized to ``0``. Thus, you can set
46 :envvar:`PYTHONY2K` to a non-empty string in the environment to require 4-digit
47 years for all year input. When 2-digit years are accepted, they are converted
48 according to the POSIX or X/Open standard: values 69-99 are mapped to 1969-1999,
49 and values 0--68 are mapped to 2000--2068. Values 100--1899 are always illegal.
50 Note that this is new as of Python 1.5.2(a2); earlier versions, up to Python
51 1.5.1 and 1.5.2a1, would add 1900 to year values below 1900.
52
Georg Brandl78f11ed2010-11-26 07:34:20 +000053.. index::
54 single: UTC
55 single: Coordinated Universal Time
56 single: Greenwich Mean Time
Georg Brandl8ec7f652007-08-15 14:28:01 +000057
58* UTC is Coordinated Universal Time (formerly known as Greenwich Mean Time, or
59 GMT). The acronym UTC is not a mistake but a compromise between English and
60 French.
61
Georg Brandl78f11ed2010-11-26 07:34:20 +000062.. index:: single: Daylight Saving Time
Georg Brandl8ec7f652007-08-15 14:28:01 +000063
64* DST is Daylight Saving Time, an adjustment of the timezone by (usually) one
65 hour during part of the year. DST rules are magic (determined by local law) and
66 can change from year to year. The C library has a table containing the local
67 rules (often it is read from a system file for flexibility) and is the only
68 source of True Wisdom in this respect.
69
70* The precision of the various real-time functions may be less than suggested by
71 the units in which their value or argument is expressed. E.g. on most Unix
Georg Brandl9af94982008-09-13 17:41:16 +000072 systems, the clock "ticks" only 50 or 100 times a second.
Georg Brandl8ec7f652007-08-15 14:28:01 +000073
Petri Lehtinen491ef972012-05-18 21:19:17 +030074* On the other hand, the precision of :func:`.time` and :func:`sleep` is better
Georg Brandl8ec7f652007-08-15 14:28:01 +000075 than their Unix equivalents: times are expressed as floating point numbers,
Petri Lehtinen491ef972012-05-18 21:19:17 +030076 :func:`.time` returns the most accurate time available (using Unix
Sandro Tosi98ed08f2012-01-14 16:42:02 +010077 :c:func:`gettimeofday` where available), and :func:`sleep` will accept a time
78 with a nonzero fraction (Unix :c:func:`select` is used to implement this, where
Georg Brandl8ec7f652007-08-15 14:28:01 +000079 available).
80
81* The time value as returned by :func:`gmtime`, :func:`localtime`, and
82 :func:`strptime`, and accepted by :func:`asctime`, :func:`mktime` and
83 :func:`strftime`, may be considered as a sequence of 9 integers. The return
84 values of :func:`gmtime`, :func:`localtime`, and :func:`strptime` also offer
85 attribute names for individual fields.
86
Georg Brandl78f11ed2010-11-26 07:34:20 +000087 See :class:`struct_time` for a description of these objects.
Georg Brandl8ec7f652007-08-15 14:28:01 +000088
89 .. versionchanged:: 2.2
90 The time value sequence was changed from a tuple to a :class:`struct_time`, with
91 the addition of attribute names for the fields.
92
Georg Brandl5c189b12009-02-27 16:59:03 +000093* Use the following functions to convert between time representations:
94
95 +-------------------------+-------------------------+-------------------------+
96 | From | To | Use |
97 +=========================+=========================+=========================+
98 | seconds since the epoch | :class:`struct_time` in | :func:`gmtime` |
99 | | UTC | |
100 +-------------------------+-------------------------+-------------------------+
101 | seconds since the epoch | :class:`struct_time` in | :func:`localtime` |
102 | | local time | |
103 +-------------------------+-------------------------+-------------------------+
104 | :class:`struct_time` in | seconds since the epoch | :func:`calendar.timegm` |
105 | UTC | | |
106 +-------------------------+-------------------------+-------------------------+
107 | :class:`struct_time` in | seconds since the epoch | :func:`mktime` |
108 | local time | | |
109 +-------------------------+-------------------------+-------------------------+
110
Georg Brandl8ec7f652007-08-15 14:28:01 +0000111
112The module defines the following functions and data items:
113
114.. data:: accept2dyear
115
116 Boolean value indicating whether two-digit year values will be accepted. This
117 is true by default, but will be set to false if the environment variable
118 :envvar:`PYTHONY2K` has been set to a non-empty string. It may also be modified
119 at run time.
120
121
122.. data:: altzone
123
124 The offset of the local DST timezone, in seconds west of UTC, if one is defined.
125 This is negative if the local DST timezone is east of UTC (as in Western Europe,
126 including the UK). Only use this if ``daylight`` is nonzero.
127
128
129.. function:: asctime([t])
130
131 Convert a tuple or :class:`struct_time` representing a time as returned by
132 :func:`gmtime` or :func:`localtime` to a 24-character string of the following
133 form: ``'Sun Jun 20 23:21:05 1993'``. If *t* is not provided, the current time
134 as returned by :func:`localtime` is used. Locale information is not used by
135 :func:`asctime`.
136
137 .. note::
138
139 Unlike the C function of the same name, there is no trailing newline.
140
141 .. versionchanged:: 2.1
142 Allowed *t* to be omitted.
143
144
145.. function:: clock()
146
147 .. index::
148 single: CPU time
149 single: processor time
150 single: benchmarking
151
152 On Unix, return the current processor time as a floating point number expressed
153 in seconds. The precision, and in fact the very definition of the meaning of
154 "processor time", depends on that of the C function of the same name, but in any
155 case, this is the function to use for benchmarking Python or timing algorithms.
156
157 On Windows, this function returns wall-clock seconds elapsed since the first
158 call to this function, as a floating point number, based on the Win32 function
Sandro Tosi98ed08f2012-01-14 16:42:02 +0100159 :c:func:`QueryPerformanceCounter`. The resolution is typically better than one
Georg Brandl8ec7f652007-08-15 14:28:01 +0000160 microsecond.
161
162
163.. function:: ctime([secs])
164
165 Convert a time expressed in seconds since the epoch to a string representing
166 local time. If *secs* is not provided or :const:`None`, the current time as
Petri Lehtinen491ef972012-05-18 21:19:17 +0300167 returned by :func:`.time` is used. ``ctime(secs)`` is equivalent to
Georg Brandl8ec7f652007-08-15 14:28:01 +0000168 ``asctime(localtime(secs))``. Locale information is not used by :func:`ctime`.
169
170 .. versionchanged:: 2.1
171 Allowed *secs* to be omitted.
172
173 .. versionchanged:: 2.4
174 If *secs* is :const:`None`, the current time is used.
175
176
177.. data:: daylight
178
179 Nonzero if a DST timezone is defined.
180
181
182.. function:: gmtime([secs])
183
184 Convert a time expressed in seconds since the epoch to a :class:`struct_time` in
185 UTC in which the dst flag is always zero. If *secs* is not provided or
Petri Lehtinen491ef972012-05-18 21:19:17 +0300186 :const:`None`, the current time as returned by :func:`.time` is used. Fractions
Georg Brandl8ec7f652007-08-15 14:28:01 +0000187 of a second are ignored. See above for a description of the
188 :class:`struct_time` object. See :func:`calendar.timegm` for the inverse of this
189 function.
190
191 .. versionchanged:: 2.1
192 Allowed *secs* to be omitted.
193
194 .. versionchanged:: 2.4
195 If *secs* is :const:`None`, the current time is used.
196
197
198.. function:: localtime([secs])
199
200 Like :func:`gmtime` but converts to local time. If *secs* is not provided or
Petri Lehtinen491ef972012-05-18 21:19:17 +0300201 :const:`None`, the current time as returned by :func:`.time` is used. The dst
Georg Brandl8ec7f652007-08-15 14:28:01 +0000202 flag is set to ``1`` when DST applies to the given time.
203
204 .. versionchanged:: 2.1
205 Allowed *secs* to be omitted.
206
207 .. versionchanged:: 2.4
208 If *secs* is :const:`None`, the current time is used.
209
210
211.. function:: mktime(t)
212
213 This is the inverse function of :func:`localtime`. Its argument is the
214 :class:`struct_time` or full 9-tuple (since the dst flag is needed; use ``-1``
215 as the dst flag if it is unknown) which expresses the time in *local* time, not
Petri Lehtinen491ef972012-05-18 21:19:17 +0300216 UTC. It returns a floating point number, for compatibility with :func:`.time`.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000217 If the input value cannot be represented as a valid time, either
218 :exc:`OverflowError` or :exc:`ValueError` will be raised (which depends on
219 whether the invalid value is caught by Python or the underlying C libraries).
220 The earliest date for which it can generate a time is platform-dependent.
221
222
223.. function:: sleep(secs)
224
225 Suspend execution for the given number of seconds. The argument may be a
226 floating point number to indicate a more precise sleep time. The actual
227 suspension time may be less than that requested because any caught signal will
228 terminate the :func:`sleep` following execution of that signal's catching
229 routine. Also, the suspension time may be longer than requested by an arbitrary
230 amount because of the scheduling of other activity in the system.
231
232
233.. function:: strftime(format[, t])
234
235 Convert a tuple or :class:`struct_time` representing a time as returned by
236 :func:`gmtime` or :func:`localtime` to a string as specified by the *format*
237 argument. If *t* is not provided, the current time as returned by
238 :func:`localtime` is used. *format* must be a string. :exc:`ValueError` is
R David Murrayec92b4a2014-06-13 17:23:34 -0400239 raised if any field in *t* is outside of the allowed range. :func:`strftime`
240 returns a locale depedent byte string; the result may be converted to unicode
241 by doing ``strftime(<myformat>).decode(locale.getlocale()[1])``.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000242
243 .. versionchanged:: 2.1
244 Allowed *t* to be omitted.
245
246 .. versionchanged:: 2.4
247 :exc:`ValueError` raised if a field in *t* is out of range.
248
249 .. versionchanged:: 2.5
250 0 is now a legal argument for any position in the time tuple; if it is normally
Zachary Ware65a64362014-07-07 15:31:21 -0500251 illegal the value is forced to a correct one.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000252
253 The following directives can be embedded in the *format* string. They are shown
254 without the optional field width and precision specification, and are replaced
255 by the indicated characters in the :func:`strftime` result:
256
257 +-----------+--------------------------------+-------+
258 | Directive | Meaning | Notes |
259 +===========+================================+=======+
260 | ``%a`` | Locale's abbreviated weekday | |
261 | | name. | |
262 +-----------+--------------------------------+-------+
263 | ``%A`` | Locale's full weekday name. | |
264 +-----------+--------------------------------+-------+
265 | ``%b`` | Locale's abbreviated month | |
266 | | name. | |
267 +-----------+--------------------------------+-------+
268 | ``%B`` | Locale's full month name. | |
269 +-----------+--------------------------------+-------+
270 | ``%c`` | Locale's appropriate date and | |
271 | | time representation. | |
272 +-----------+--------------------------------+-------+
273 | ``%d`` | Day of the month as a decimal | |
274 | | number [01,31]. | |
275 +-----------+--------------------------------+-------+
276 | ``%H`` | Hour (24-hour clock) as a | |
277 | | decimal number [00,23]. | |
278 +-----------+--------------------------------+-------+
279 | ``%I`` | Hour (12-hour clock) as a | |
280 | | decimal number [01,12]. | |
281 +-----------+--------------------------------+-------+
282 | ``%j`` | Day of the year as a decimal | |
283 | | number [001,366]. | |
284 +-----------+--------------------------------+-------+
285 | ``%m`` | Month as a decimal number | |
286 | | [01,12]. | |
287 +-----------+--------------------------------+-------+
288 | ``%M`` | Minute as a decimal number | |
289 | | [00,59]. | |
290 +-----------+--------------------------------+-------+
291 | ``%p`` | Locale's equivalent of either | \(1) |
292 | | AM or PM. | |
293 +-----------+--------------------------------+-------+
294 | ``%S`` | Second as a decimal number | \(2) |
295 | | [00,61]. | |
296 +-----------+--------------------------------+-------+
297 | ``%U`` | Week number of the year | \(3) |
298 | | (Sunday as the first day of | |
299 | | the week) as a decimal number | |
300 | | [00,53]. All days in a new | |
301 | | year preceding the first | |
302 | | Sunday are considered to be in | |
303 | | week 0. | |
304 +-----------+--------------------------------+-------+
305 | ``%w`` | Weekday as a decimal number | |
306 | | [0(Sunday),6]. | |
307 +-----------+--------------------------------+-------+
308 | ``%W`` | Week number of the year | \(3) |
309 | | (Monday as the first day of | |
310 | | the week) as a decimal number | |
311 | | [00,53]. All days in a new | |
312 | | year preceding the first | |
313 | | Monday are considered to be in | |
314 | | week 0. | |
315 +-----------+--------------------------------+-------+
316 | ``%x`` | Locale's appropriate date | |
317 | | representation. | |
318 +-----------+--------------------------------+-------+
319 | ``%X`` | Locale's appropriate time | |
320 | | representation. | |
321 +-----------+--------------------------------+-------+
322 | ``%y`` | Year without century as a | |
323 | | decimal number [00,99]. | |
324 +-----------+--------------------------------+-------+
325 | ``%Y`` | Year with century as a decimal | |
326 | | number. | |
327 +-----------+--------------------------------+-------+
328 | ``%Z`` | Time zone name (no characters | |
329 | | if no time zone exists). | |
330 +-----------+--------------------------------+-------+
331 | ``%%`` | A literal ``'%'`` character. | |
332 +-----------+--------------------------------+-------+
333
334 Notes:
335
336 (1)
337 When used with the :func:`strptime` function, the ``%p`` directive only affects
338 the output hour field if the ``%I`` directive is used to parse the hour.
339
340 (2)
341 The range really is ``0`` to ``61``; this accounts for leap seconds and the
342 (very rare) double leap seconds.
343
344 (3)
345 When used with the :func:`strptime` function, ``%U`` and ``%W`` are only used in
346 calculations when the day of the week and the year are specified.
347
348 Here is an example, a format for dates compatible with that specified in the
349 :rfc:`2822` Internet email standard. [#]_ ::
350
351 >>> from time import gmtime, strftime
352 >>> strftime("%a, %d %b %Y %H:%M:%S +0000", gmtime())
353 'Thu, 28 Jun 2001 14:17:15 +0000'
354
Georg Brandl1b1c11d2013-10-13 18:28:25 +0200355 Additional directives may be supported on certain platforms, but only the
356 ones listed here have a meaning standardized by ANSI C. To see the full set
357 of format codes supported on your platform, consult the :manpage:`strftime(3)`
358 documentation.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000359
360 On some platforms, an optional field width and precision specification can
361 immediately follow the initial ``'%'`` of a directive in the following order;
362 this is also not portable. The field width is normally 2 except for ``%j`` where
363 it is 3.
364
365
366.. function:: strptime(string[, format])
367
368 Parse a string representing a time according to a format. The return value is
369 a :class:`struct_time` as returned by :func:`gmtime` or :func:`localtime`.
370
371 The *format* parameter uses the same directives as those used by
372 :func:`strftime`; it defaults to ``"%a %b %d %H:%M:%S %Y"`` which matches the
373 formatting returned by :func:`ctime`. If *string* cannot be parsed according to
374 *format*, or if it has excess data after parsing, :exc:`ValueError` is raised.
375 The default values used to fill in any missing data when more accurate values
376 cannot be inferred are ``(1900, 1, 1, 0, 0, 0, 0, 1, -1)``.
377
Georg Brandle8f1b002008-03-22 22:04:10 +0000378 For example:
Georg Brandl8ec7f652007-08-15 14:28:01 +0000379
380 >>> import time
Georg Brandle8f1b002008-03-22 22:04:10 +0000381 >>> time.strptime("30 Nov 00", "%d %b %y") # doctest: +NORMALIZE_WHITESPACE
382 time.struct_time(tm_year=2000, tm_mon=11, tm_mday=30, tm_hour=0, tm_min=0,
383 tm_sec=0, tm_wday=3, tm_yday=335, tm_isdst=-1)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000384
385 Support for the ``%Z`` directive is based on the values contained in ``tzname``
386 and whether ``daylight`` is true. Because of this, it is platform-specific
387 except for recognizing UTC and GMT which are always known (and are considered to
388 be non-daylight savings timezones).
389
390 Only the directives specified in the documentation are supported. Because
391 ``strftime()`` is implemented per platform it can sometimes offer more
392 directives than those listed. But ``strptime()`` is independent of any platform
393 and thus does not necessarily support all directives available that are not
394 documented as supported.
395
396
Georg Brandl78f11ed2010-11-26 07:34:20 +0000397.. class:: struct_time
Georg Brandl8ec7f652007-08-15 14:28:01 +0000398
399 The type of the time value sequence returned by :func:`gmtime`,
Georg Brandl78f11ed2010-11-26 07:34:20 +0000400 :func:`localtime`, and :func:`strptime`. It is an object with a :term:`named
401 tuple` interface: values can be accessed by index and by attribute name. The
402 following values are present:
403
404 +-------+-------------------+---------------------------------+
405 | Index | Attribute | Values |
406 +=======+===================+=================================+
407 | 0 | :attr:`tm_year` | (for example, 1993) |
408 +-------+-------------------+---------------------------------+
409 | 1 | :attr:`tm_mon` | range [1, 12] |
410 +-------+-------------------+---------------------------------+
411 | 2 | :attr:`tm_mday` | range [1, 31] |
412 +-------+-------------------+---------------------------------+
413 | 3 | :attr:`tm_hour` | range [0, 23] |
414 +-------+-------------------+---------------------------------+
415 | 4 | :attr:`tm_min` | range [0, 59] |
416 +-------+-------------------+---------------------------------+
Sandro Tosi51a5ad42012-04-25 19:55:30 +0200417 | 5 | :attr:`tm_sec` | range [0, 61]; see **(2)** in |
Georg Brandl78f11ed2010-11-26 07:34:20 +0000418 | | | :func:`strftime` description |
419 +-------+-------------------+---------------------------------+
420 | 6 | :attr:`tm_wday` | range [0, 6], Monday is 0 |
421 +-------+-------------------+---------------------------------+
422 | 7 | :attr:`tm_yday` | range [1, 366] |
423 +-------+-------------------+---------------------------------+
424 | 8 | :attr:`tm_isdst` | 0, 1 or -1; see below |
425 +-------+-------------------+---------------------------------+
Georg Brandl8ec7f652007-08-15 14:28:01 +0000426
427 .. versionadded:: 2.2
428
Georg Brandl78f11ed2010-11-26 07:34:20 +0000429 Note that unlike the C structure, the month value is a range of [1, 12], not
430 [0, 11]. A year value will be handled as described under :ref:`Year 2000
431 (Y2K) issues <time-y2kissues>` above. A ``-1`` argument as the daylight
432 savings flag, passed to :func:`mktime` will usually result in the correct
433 daylight savings state to be filled in.
434
435 When a tuple with an incorrect length is passed to a function expecting a
436 :class:`struct_time`, or having elements of the wrong type, a
437 :exc:`TypeError` is raised.
438
Georg Brandl8ec7f652007-08-15 14:28:01 +0000439
440.. function:: time()
441
R David Murray32a3b142012-03-15 03:05:01 -0400442 Return the time in seconds since the epoch as a floating point number.
443 Note that even though the time is always returned as a floating point
Georg Brandl8ec7f652007-08-15 14:28:01 +0000444 number, not all systems provide time with a better precision than 1 second.
445 While this function normally returns non-decreasing values, it can return a
446 lower value than a previous call if the system clock has been set back between
447 the two calls.
448
449
450.. data:: timezone
451
452 The offset of the local (non-DST) timezone, in seconds west of UTC (negative in
453 most of Western Europe, positive in the US, zero in the UK).
454
455
456.. data:: tzname
457
458 A tuple of two strings: the first is the name of the local non-DST timezone, the
459 second is the name of the local DST timezone. If no DST timezone is defined,
460 the second string should not be used.
461
462
463.. function:: tzset()
464
465 Resets the time conversion rules used by the library routines. The environment
466 variable :envvar:`TZ` specifies how this is done.
467
468 .. versionadded:: 2.3
469
470 Availability: Unix.
471
472 .. note::
473
474 Although in many cases, changing the :envvar:`TZ` environment variable may
475 affect the output of functions like :func:`localtime` without calling
476 :func:`tzset`, this behavior should not be relied on.
477
478 The :envvar:`TZ` environment variable should contain no whitespace.
479
480 The standard format of the :envvar:`TZ` environment variable is (whitespace
481 added for clarity)::
482
483 std offset [dst [offset [,start[/time], end[/time]]]]
484
485 Where the components are:
486
487 ``std`` and ``dst``
488 Three or more alphanumerics giving the timezone abbreviations. These will be
489 propagated into time.tzname
490
491 ``offset``
492 The offset has the form: ``± hh[:mm[:ss]]``. This indicates the value
493 added the local time to arrive at UTC. If preceded by a '-', the timezone
494 is east of the Prime Meridian; otherwise, it is west. If no offset follows
495 dst, summer time is assumed to be one hour ahead of standard time.
496
497 ``start[/time], end[/time]``
498 Indicates when to change to and back from DST. The format of the
499 start and end dates are one of the following:
500
501 :samp:`J{n}`
502 The Julian day *n* (1 <= *n* <= 365). Leap days are not counted, so in
503 all years February 28 is day 59 and March 1 is day 60.
504
505 :samp:`{n}`
506 The zero-based Julian day (0 <= *n* <= 365). Leap days are counted, and
507 it is possible to refer to February 29.
508
509 :samp:`M{m}.{n}.{d}`
510 The *d*'th day (0 <= *d* <= 6) or week *n* of month *m* of the year (1
511 <= *n* <= 5, 1 <= *m* <= 12, where week 5 means "the last *d* day in
512 month *m*" which may occur in either the fourth or the fifth
513 week). Week 1 is the first week in which the *d*'th day occurs. Day
514 zero is Sunday.
515
516 ``time`` has the same format as ``offset`` except that no leading sign
517 ('-' or '+') is allowed. The default, if time is not given, is 02:00:00.
518
519 ::
520
521 >>> os.environ['TZ'] = 'EST+05EDT,M4.1.0,M10.5.0'
522 >>> time.tzset()
523 >>> time.strftime('%X %x %Z')
524 '02:07:36 05/08/03 EDT'
525 >>> os.environ['TZ'] = 'AEST-10AEDT-11,M10.5.0,M3.5.0'
526 >>> time.tzset()
527 >>> time.strftime('%X %x %Z')
528 '16:08:12 05/08/03 AEST'
529
530 On many Unix systems (including \*BSD, Linux, Solaris, and Darwin), it is more
531 convenient to use the system's zoneinfo (:manpage:`tzfile(5)`) database to
532 specify the timezone rules. To do this, set the :envvar:`TZ` environment
533 variable to the path of the required timezone datafile, relative to the root of
534 the systems 'zoneinfo' timezone database, usually located at
535 :file:`/usr/share/zoneinfo`. For example, ``'US/Eastern'``,
536 ``'Australia/Melbourne'``, ``'Egypt'`` or ``'Europe/Amsterdam'``. ::
537
538 >>> os.environ['TZ'] = 'US/Eastern'
539 >>> time.tzset()
540 >>> time.tzname
541 ('EST', 'EDT')
542 >>> os.environ['TZ'] = 'Egypt'
543 >>> time.tzset()
544 >>> time.tzname
545 ('EET', 'EEST')
546
547
548.. seealso::
549
550 Module :mod:`datetime`
551 More object-oriented interface to dates and times.
552
553 Module :mod:`locale`
Terry Jan Reedyc2f905f2013-04-03 12:34:57 -0400554 Internationalization services. The locale setting affects the interpretation
Terry Jan Reedy0d0a3952013-04-03 12:45:24 -0400555 of many format specifiers in :func:`strftime` and :func:`strptime`.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000556
557 Module :mod:`calendar`
Serhiy Storchakab33336f2013-10-13 23:09:00 +0300558 General calendar-related functions. :func:`~calendar.timegm` is the
559 inverse of :func:`gmtime` from this module.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000560
561.. rubric:: Footnotes
562
563.. [#] The use of ``%Z`` is now deprecated, but the ``%z`` escape that expands to the
564 preferred hour/minute offset is not supported by all ANSI C libraries. Also, a
565 strict reading of the original 1982 :rfc:`822` standard calls for a two-digit
566 year (%y rather than %Y), but practice moved to 4-digit years long before the
Sandro Tosi657a7fc2011-08-19 18:39:35 +0200567 year 2000. After that, :rfc:`822` became obsolete and the 4-digit year has
568 been first recommended by :rfc:`1123` and then mandated by :rfc:`2822`.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000569