Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit abc8cc6

Browse files
committed
Move some \index entries around so we can avoid using empty comments;
empty comments trigger a bug in LaTeX2HTML. Problem reported by Gerry Wiener <[email protected]>.
1 parent 82f355a commit abc8cc6

1 file changed

Lines changed: 25 additions & 31 deletions

File tree

Doc/lib/libtime.tex

Lines changed: 25 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -16,23 +16,22 @@ \section{\module{time} ---
1616
The \dfn{epoch}\index{epoch} is the point where the time starts. On
1717
January 1st of that year, at 0 hours, the ``time since the epoch'' is
1818
zero. For \UNIX{}, the epoch is 1970. To find out what the epoch is,
19-
look at \code{gmtime(0)}.%
20-
\index{epoch}
19+
look at \code{gmtime(0)}.
2120

2221
\item
2322
The functions in this module do not handle dates and times before the
2423
epoch or far in the future. The cut-off point in the future is
25-
determined by the \C{} library; for \UNIX{}, it is typically in 2038.%
26-
\index{Year 2038}
24+
determined by the C library; for \UNIX{}, it is typically in
25+
2038\index{Year 2038}.
2726

2827
\item
29-
\strong{Year 2000 (Y2K) issues}: Python depends on the platform's \C{}
30-
library, which generally doesn't have year 2000 issues, since all
31-
dates and times are represented internally as seconds since the
32-
epoch. Functions accepting a time tuple (see below) generally require
33-
a 4-digit year. For backward compatibility, 2-digit years are
34-
supported if the module variable \code{accept2dyear} is a non-zero
35-
integer; this variable is initialized to \code{1} unless the
28+
\strong{Year 2000 (Y2K) issues}:\index{Year 2000}\index{Y2K} Python
29+
depends on the platform's C library, which generally doesn't have year
30+
2000 issues, since all dates and times are represented internally as
31+
seconds since the epoch. Functions accepting a time tuple (see below)
32+
generally require a 4-digit year. For backward compatibility, 2-digit
33+
years are supported if the module variable \code{accept2dyear} is a
34+
non-zero integer; this variable is initialized to \code{1} unless the
3635
environment variable \envvar{PYTHONY2K} is set to a non-empty string,
3736
in which case it is initialized to \code{0}. Thus, you can set
3837
\envvar{PYTHONY2K} to a non-empty string in the environment to require 4-digit
@@ -41,26 +40,21 @@ \section{\module{time} ---
4140
are mapped to 1969-1999, and values 0--68 are mapped to 2000--2068.
4241
Values 100--1899 are always illegal. Note that this is new as of
4342
Python 1.5.2(a2); earlier versions, up to Python 1.5.1 and 1.5.2a1,
44-
would add 1900 to year values below 1900.%
45-
\index{Year 2000}%
46-
\index{Y2K}
43+
would add 1900 to year values below 1900.
4744

4845
\item
49-
UTC is Coordinated Universal Time (formerly known as Greenwich Mean
50-
Time, or GMT). The acronym UTC is not a mistake but a compromise
51-
between English and French.%
52-
\index{UTC}%
53-
\index{Coordinated Universal Time}%
54-
\index{Greenwich Mean Time}
46+
UTC\index{UTC} is Coordinated Universal Time\index{Coordinated
47+
Universal Time} (formerly known as Greenwich Mean
48+
Time,\index{Greenwich Mean Time} or GMT). The acronym UTC is not a
49+
mistake but a compromise between English and French.
5550

5651
\item
57-
DST is Daylight Saving Time, an adjustment of the timezone by
58-
(usually) one hour during part of the year. DST rules are magic
59-
(determined by local law) and can change from year to year. The \C{}
60-
library has a table containing the local rules (often it is read from
61-
a system file for flexibility) and is the only source of True Wisdom
62-
in this respect.%
63-
\index{Daylight Saving Time}
52+
DST is Daylight Saving Time,\index{Daylight Saving Time} an adjustment
53+
of the timezone by (usually) one hour during part of the year. DST
54+
rules are magic (determined by local law) and can change from year to
55+
year. The C library has a table containing the local rules (often it
56+
is read from a system file for flexibility) and is the only source of
57+
True Wisdom in this respect.
6458

6559
\item
6660
The precision of the various real-time functions may be less than
@@ -84,7 +78,7 @@ \section{\module{time} ---
8478
is a tuple of 9 integers: year (e.g.\ 1993), month (1--12), day
8579
(1--31), hour (0--23), minute (0--59), second (0--59), weekday (0--6,
8680
monday is 0), Julian day (1--366) and daylight savings flag (-1, 0 or
87-
1). Note that unlike the \C{} structure, the month value is a range
81+
1). Note that unlike the C structure, the month value is a range
8882
of 1-12, not 0-11. A year value will be handled as descibed under
8983
``Year 2000 (Y2K) issues'' above. A \code{-1} argument as daylight
9084
savings flag, passed to \function{mktime()} will usually result in the
@@ -112,14 +106,14 @@ \section{\module{time} ---
112106
\begin{funcdesc}{asctime}{tuple}
113107
Convert a tuple representing a time as returned by \function{gmtime()}
114108
or \function{localtime()} to a 24-character string of the following form:
115-
\code{'Sun Jun 20 23:21:05 1993'}. Note: unlike the \C{} function of
109+
\code{'Sun Jun 20 23:21:05 1993'}. Note: unlike the C function of
116110
the same name, there is no trailing newline.
117111
\end{funcdesc}
118112

119113
\begin{funcdesc}{clock}{}
120114
Return the current CPU time as a floating point number expressed in
121115
seconds. The precision, and in fact the very definiton of the meaning
122-
of ``CPU time''\index{CPU time}, depends on that of the \C{} function
116+
of ``CPU time''\index{CPU time}, depends on that of the C function
123117
of the same name, but in any case, this is the function to use for
124118
benchmarking\index{benchmarking} Python or timing algorithms.
125119
\end{funcdesc}
@@ -199,7 +193,7 @@ \section{\module{time} ---
199193
\end{tableii}
200194

201195
Additional directives may be supported on certain platforms, but
202-
only the ones listed here have a meaning standardized by ANSI \C{}.
196+
only the ones listed here have a meaning standardized by ANSI C.
203197

204198
On some platforms, an optional field width and precision
205199
specification can immediately follow the initial \character{\%} of a

0 commit comments

Comments
 (0)