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

Skip to content

Commit c589124

Browse files
freddrakefreddrake
committed
Use the new RFC macros wherever RFCs are referenced by number. No other
changes.
1 parent b16166e commit c589124

24 files changed

Lines changed: 56 additions & 58 deletions

‎Doc/lib/libbase64.tex‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@ \section{Standard Module \sectcode{base64}}
22
\label{module-base64}
33
\stmodindex{base64}
44
\indexii{base-64}{encoding}
5-
\index{RFC!1421}
5+
\rfcindex{1421}
66
\index{MIME!base 64 encoding}
77

88
This module perform base-64 encoding and decoding of arbitrary binary
99
strings into text strings that can be safely emailed or posted. The
10-
encoding scheme is defined in RFC 1421 and is used for MIME email and
10+
encoding scheme is defined in \rfc{1421} and is used for MIME email and
1111
various other Internet-related applications; it is not the same as the
1212
output produced by the \file{uuencode} program. For example, the
1313
string \code{'www.python.org'} is encoded as the string

‎Doc/lib/libftplib.tex‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ \section{Standard Module \sectcode{ftplib}}
22
\label{module-ftplib}
33
\stmodindex{ftplib}
44
\indexii{FTP}{protocol}
5-
\index{RFC!959}
5+
\rfcindex{959}
66

77
\renewcommand{\indexsubitem}{(in module ftplib)}
88

@@ -11,8 +11,7 @@ \section{Standard Module \sectcode{ftplib}}
1111
can use this to write Python programs that perform a variety of
1212
automated FTP jobs, such as mirroring other ftp servers. It is also
1313
used by the module \code{urllib} to handle URLs that use FTP. For
14-
more information on FTP (File Transfer Protocol), see Internet RFC
15-
959.
14+
more information on FTP (File Transfer Protocol), see Internet \rfc{959}.
1615

1716
Here's a sample session using the \code{ftplib} module:
1817

‎Doc/lib/libhtmllib.tex‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
\section{Standard Module \sectcode{htmllib}}
22
\label{module-htmllib}
33
\stmodindex{htmllib}
4+
\rfcindex{1866}
45
\index{HTML}
56
\index{hypertext}
67

@@ -63,7 +64,7 @@ \section{Standard Module \sectcode{htmllib}}
6364

6465
\begin{funcdesc}{HTMLParser}{formatter}
6566
This is the basic HTML parser class. It supports all entity names
66-
required by the HTML 2.0 specification (RFC 1866). It also defines
67+
required by the HTML 2.0 specification (\rfc{1866}). It also defines
6768
handlers for all HTML 2.0 and many HTML 3.0 and 3.2 elements.
6869
\end{funcdesc}
6970

‎Doc/lib/libhttplib.tex‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ \subsection{HTTP Objects}
7979
\end{funcdesc}
8080

8181
\begin{funcdesc}{putheader}{header\, argument\optional{\, ...}}
82-
Send an RFC-822 style header to the server. It sends a line to the
82+
Send an \rfc{822} style header to the server. It sends a line to the
8383
server consisting of the header, a colon and a space, and the first
8484
argument. If more arguments are given, continuation lines are sent,
8585
each consisting of a tab and an argument.

‎Doc/lib/libmailcap.tex‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
\section{Standard Module \sectcode{mailcap}}
22
\label{module-mailcap}
3+
\rfcindex{1524}
34
\stmodindex{mailcap}
45
\renewcommand{\indexsubitem}{(in module mailcap)}
56

@@ -12,7 +13,7 @@ \section{Standard Module \sectcode{mailcap}}
1213
replaced by a filename (usually one belonging to a temporary file) and
1314
the xmpeg program can be automatically started to view the file.
1415

15-
The mailcap format is documented in RFC 1524, ``A User Agent
16+
The mailcap format is documented in \rfc{1524}, ``A User Agent
1617
Configuration Mechanism For Multimedia Mail Format Information'', but
1718
is not an Internet standard. However, mailcap files are supported on
1819
most \UNIX{} systems.
@@ -24,12 +25,13 @@ \section{Standard Module \sectcode{mailcap}}
2425
the mailcap entry for a given MIME type. If no matching MIME
2526
type can be found, \code{(None, None)} is returned.
2627

27-
\var{key} is the name of the field desired, which represents the type of
28-
activity to be performed; the default value is 'view', since in the
28+
\var{key} is the name of the field desired, which represents the type
29+
of activity to be performed; the default value is 'view', since in the
2930
most common case you simply want to view the body of the MIME-typed
3031
data. Other possible values might be 'compose' and 'edit', if you
3132
wanted to create a new body of the given MIME type or alter the
32-
existing body data. See RFC1524 for a complete list of these fields.
33+
existing body data. See \rfc{1524} for a complete list of these
34+
fields.
3335

3436
\var{filename} is the filename to be substituted for \%s in the
3537
command line; the default value is

‎Doc/lib/libmd5.tex‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
\section{Built-in Module \sectcode{md5}}
22
\label{module-md5}
3+
\rfcindex{1321}
34
\bimodindex{md5}
45

56
This module implements the interface to RSA's MD5 message digest
6-
algorithm (see also Internet RFC 1321). Its use is quite
7+
algorithm (see also Internet \rfc{1321}). Its use is quite
78
straightforward:\ use the \code{md5.new()} to create an md5 object.
89
You can now feed this object with arbitrary strings using the
910
\code{update()} method, and at any point you can ask it for the

‎Doc/lib/libnntplib.tex‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@ \section{Standard Module \sectcode{nntplib}}
22
\label{module-nntplib}
33
\stmodindex{nntplib}
44
\indexii{NNTP}{protocol}
5-
\index{RFC!977}
5+
\rfcindex{977}
66

77
\renewcommand{\indexsubitem}{(in module nntplib)}
88

99
This module defines the class \code{NNTP} which implements the client
1010
side of the NNTP protocol. It can be used to implement a news reader
1111
or poster, or automated news processors. For more information on NNTP
12-
(Network News Transfer Protocol), see Internet RFC 977.
12+
(Network News Transfer Protocol), see Internet \rfc{977}.
1313

1414
Here are two small examples of how it can be used. To list some
1515
statistics about a newsgroup and print the subjects of the last 10

‎Doc/lib/libquopri.tex‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,12 @@ \section{Standard Module \sectcode{quopri}}
33
\stmodindex{quopri}
44

55
This module performs quoted-printable transport encoding and decoding,
6-
as defined in RFC 1521: ``MIME (Multipurpose Internet Mail Extensions)
6+
as defined in \rfc{1521}: ``MIME (Multipurpose Internet Mail Extensions)
77
Part One''. The quoted-printable encoding is designed for data where
88
there are relatively few nonprintable characters; the base-64 encoding
99
scheme available via the \code{base64} module is more compact if there
1010
are many such characters, as when sending a graphics file.
1111
\indexii{quoted printable}{encoding}
12-
\indexii{RFC}{1521}
1312
\index{MIME!quoted-printable encoding}
1413

1514
\renewcommand{\indexsubitem}{(in module quopri)}

‎Doc/lib/librfc822.tex‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,8 @@ \section{Standard Module \sectcode{rfc822}}
66

77
This module defines a class, \code{Message}, which represents a
88
collection of ``email headers'' as defined by the Internet standard
9-
RFC 822. It is used in various contexts, usually to read such headers
10-
from a file.
11-
\index{RFC!822}
9+
\rfc{822}. It is used in various contexts, usually to read such
10+
headers from a file.
1211

1312
Note that there's a separate module to read \UNIX{}, MH, and MMDF
1413
style mailbox files: \code{mailbox}.
@@ -30,10 +29,10 @@ \section{Standard Module \sectcode{rfc822}}
3029
the same result.
3130

3231
\begin{funcdesc}{parsedate}{date}
33-
Attempts to parse a date according to the rules in RFC822. however,
32+
Attempts to parse a date according to the rules in \rfc{822}. however,
3433
some mailers don't follow that format as specified, so
3534
\code{parsedate()} tries to guess correctly in such cases.
36-
\var{date} is a string containing an RFC822 date, such as
35+
\var{date} is a string containing an \rfc{822} date, such as
3736
\code{"Mon, 20 Nov 1995 19:12:08 -0500"}. If it succeeds in parsing
3837
the date, \code{parsedate()} returns a 9-tuple that can be passed
3938
directly to \code{time.mktime()}; otherwise \code{None} will be

‎Doc/lib/liburlparse.tex‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,8 @@ \section{Standard Module \sectcode{urlparse}}
1616

1717
The module has been designed to match the Internet RFC on Relative
1818
Uniform Resource Locators (and discovered a bug in an earlier
19-
draft!). Refer to RFC 1808\index{RFC!1808} for details on relative
20-
URLs and RFC 1738\index{RFC!1738} for information on basic URL
21-
syntax.
19+
draft!). Refer to \rfc{1808} for details on relative
20+
URLs and \rfc{1738} for information on basic URL syntax.
2221

2322
It defines the following functions:
2423

0 commit comments

Comments
 (0)