mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-09-26 18:29:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

Update comment about relative URL internet draft to reflect current RFC status;

Browse source 
index references the appropriate RFCs.

Consistency:  Always use trailing "()" on function names in running text.
This commit is contained in:
Fred Drake 1998-01-21 04:55:02 +00:00
parent c210e69981
commit d1cc9c2b92
2 changed files with 14 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

12
Doc/lib/liburlparse.tex
View file

@ -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 the components back into a URL string, and to convert a ``relative
URL'' to an absolute URL given a ``base URL''. URL'' to an absolute URL given a ``base URL''.
The module has been designed to match the current Internet draft on The module has been designed to match the Internet RFC on Relative
Relative Uniform Resource Locators (and discovered a bug in an earlier Uniform Resource Locators (and discovered a bug in an earlier
draft!). 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: It defines the following functions:
@ -54,7 +56,7 @@ support them. The default value for this argument is \code{1}.
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{urlunparse}{tuple} \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 This may result in a slightly different, but equivalent URL, if the
URL that was parsed originally had redundant delimiters, e.g. a ? with URL that was parsed originally had redundant delimiters, e.g. a ? with
an empty query (the draft states that these are equivalent). an empty query (the draft states that these are equivalent).
@ -80,5 +82,5 @@ yields the string
\end{verbatim}\ecode \end{verbatim}\ecode
% %
The \var{allow_fragments} argument has the same meaning as for The \var{allow_fragments} argument has the same meaning as for
\code{urlparse}. \code{urlparse()}.
\end{funcdesc} \end{funcdesc}

12
Doc/liburlparse.tex
View file

@ -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 the components back into a URL string, and to convert a ``relative
URL'' to an absolute URL given a ``base URL''. URL'' to an absolute URL given a ``base URL''.
The module has been designed to match the current Internet draft on The module has been designed to match the Internet RFC on Relative
Relative Uniform Resource Locators (and discovered a bug in an earlier Uniform Resource Locators (and discovered a bug in an earlier
draft!). 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: It defines the following functions:
@ -54,7 +56,7 @@ support them. The default value for this argument is \code{1}.
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{urlunparse}{tuple} \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 This may result in a slightly different, but equivalent URL, if the
URL that was parsed originally had redundant delimiters, e.g. a ? with URL that was parsed originally had redundant delimiters, e.g. a ? with
an empty query (the draft states that these are equivalent). an empty query (the draft states that these are equivalent).
@ -80,5 +82,5 @@ yields the string
\end{verbatim}\ecode \end{verbatim}\ecode
% %
The \var{allow_fragments} argument has the same meaning as for The \var{allow_fragments} argument has the same meaning as for
\code{urlparse}. \code{urlparse()}.
\end{funcdesc} \end{funcdesc}