summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1998-01-21 04:55:02 (GMT)
committerFred Drake <fdrake@acm.org>1998-01-21 04:55:02 (GMT)
commitd1cc9c2b925971870bcba26543feca57d5846579 (patch)
tree76733529658519535d582d8bb9c0a0b42b7bc5ab
parentc210e69981f2fbacfe72d04df4a3b8f2306b8f33 (diff)
downloadcpython-d1cc9c2b925971870bcba26543feca57d5846579.zip
cpython-d1cc9c2b925971870bcba26543feca57d5846579.tar.gz
cpython-d1cc9c2b925971870bcba26543feca57d5846579.tar.bz2
Update comment about relative URL internet draft to reflect current RFC status;
index references the appropriate RFCs. Consistency: Always use trailing "()" on function names in running text.
-rw-r--r--Doc/lib/liburlparse.tex12
-rw-r--r--Doc/liburlparse.tex12
2 files changed, 14 insertions, 10 deletions
diff --git a/Doc/lib/liburlparse.tex b/Doc/lib/liburlparse.tex
index bfd1c0d..9582bbe 100644
--- a/Doc/lib/liburlparse.tex
+++ b/Doc/lib/liburlparse.tex
@@ -14,9 +14,11 @@ components (addessing scheme, network location, path etc.), to combine
the components back into a URL string, and to convert a ``relative
URL'' to an absolute URL given a ``base URL''.
-The module has been designed to match the current Internet draft on
-Relative Uniform Resource Locators (and discovered a bug in an earlier
-draft!).
+The module has been designed to match the Internet RFC on Relative
+Uniform Resource Locators (and discovered a bug in an earlier
+draft!). Refer to RFC 1808\index{RFC!1808} for details on relative
+URLs and RFC 1738\index{RFC!1738} for information on basic URL
+syntax.
It defines the following functions:
@@ -54,7 +56,7 @@ support them. The default value for this argument is \code{1}.
\end{funcdesc}
\begin{funcdesc}{urlunparse}{tuple}
-Construct a URL string from a tuple as returned by \code{urlparse}.
+Construct a URL string from a tuple as returned by \code{urlparse()}.
This may result in a slightly different, but equivalent URL, if the
URL that was parsed originally had redundant delimiters, e.g. a ? with
an empty query (the draft states that these are equivalent).
@@ -80,5 +82,5 @@ yields the string
\end{verbatim}\ecode
%
The \var{allow_fragments} argument has the same meaning as for
-\code{urlparse}.
+\code{urlparse()}.
\end{funcdesc}
diff --git a/Doc/liburlparse.tex b/Doc/liburlparse.tex
index bfd1c0d..9582bbe 100644
--- a/Doc/liburlparse.tex
+++ b/Doc/liburlparse.tex
@@ -14,9 +14,11 @@ components (addessing scheme, network location, path etc.), to combine
the components back into a URL string, and to convert a ``relative
URL'' to an absolute URL given a ``base URL''.
-The module has been designed to match the current Internet draft on
-Relative Uniform Resource Locators (and discovered a bug in an earlier
-draft!).
+The module has been designed to match the Internet RFC on Relative
+Uniform Resource Locators (and discovered a bug in an earlier
+draft!). Refer to RFC 1808\index{RFC!1808} for details on relative
+URLs and RFC 1738\index{RFC!1738} for information on basic URL
+syntax.
It defines the following functions:
@@ -54,7 +56,7 @@ support them. The default value for this argument is \code{1}.
\end{funcdesc}
\begin{funcdesc}{urlunparse}{tuple}
-Construct a URL string from a tuple as returned by \code{urlparse}.
+Construct a URL string from a tuple as returned by \code{urlparse()}.
This may result in a slightly different, but equivalent URL, if the
URL that was parsed originally had redundant delimiters, e.g. a ? with
an empty query (the draft states that these are equivalent).
@@ -80,5 +82,5 @@ yields the string
\end{verbatim}\ecode
%
The \var{allow_fragments} argument has the same meaning as for
-\code{urlparse}.
+\code{urlparse()}.
\end{funcdesc}