The underlying C library determines the range of dates that the
time module can handle. On Unix systems, years 1970 and 2038 are typical cut-off points, a limitation that
mx.DateTime let you avoid. Time instants are normally specified in UTC (Coordinated Universal Time, once known as GMT, or Greenwich Mean Time). Module
time also supports local time zones and daylight saving time (DST), but only to the extent that support is supplied by the underlying C system library.
As an alternative to seconds since the epoch, a time instant can be represented by a tuple of nine integers, called a time-tuple. (Time-tuples are covered in Table 12-1.) All items are integers: time-tuples don’t keep track of fractions of a second. A time-tuple is an instance of
struct_time. You can use it as a tuple, and access the items as read-only attributes
.tm_mon, and so on, with the attribute names listed in Table 12-1. Wherever a function requires a time-tuple argument, you can pass an instance of
struct_time or any other sequence whose items are nine integers in the right ranges.
Table 12-1. Tuple form of time representation
Wider on some platforms.
Day number within the year.