address review

Author: lpyu001

Doc/library/urllib.parse.rst

@@ -125,7 +125,7 @@ or on combining URL components into a URL string.
 
    If the *allow_fragments* argument is false, fragment identifiers are not
    recognized.  Instead, they are parsed as part of the path
-   or query component, and :attr:`fragment <SplitResult.fragment>` is set to
+   or query component, and :attr:`~SplitResult.fragment` is set to
    ``None`` or the empty
    string (depending on the value of *missing_as_none*) in the return value.
 
@@ -158,16 +158,16 @@ or on combining URL components into a URL string.
 
    .. [1] Depending on the value of the *missing_as_none* argument.
 
-   Reading the :attr:`port <SplitResult.port>` attribute will raise a
+   Reading the :attr:`~SplitResult.port` attribute will raise a
    :exc:`ValueError` if
    an invalid port is specified in the URL.  See section
    :ref:`urlparse-result-object` for more information on the result object.
 
-   Unmatched square brackets in the :attr:`netloc <SplitResult.netloc>`
+   Unmatched square brackets in the :attr:`~SplitResult.netloc`
    attribute will raise a
    :exc:`ValueError`.
 
-   Characters in the :attr:`netloc <SplitResult.netloc>` attribute that
+   Characters in the :attr:`~SplitResult.netloc` attribute that
    decompose under NFKC
    normalization (as used by the IDNA encoding) into any of ``/``, ``?``,
    ``#``, ``@``, or ``:`` will raise a :exc:`ValueError`. If the URL is
@@ -512,15 +512,15 @@ byte values will trigger :exc:`UnicodeDecodeError`.
 
 To support easier conversion of result objects between :class:`str` and
 :class:`bytes`, all return values from URL parsing functions provide
-either an :meth:`encode <DefragResult.encode>` method (when the result contains
-:class:`str` data) or a :meth:`decode <DefragResultBytes.decode>` method (when
+either an :meth:`~DefragResult.encode` method (when the result contains
+:class:`str` data) or a :meth:`~DefragResultBytes.decode` method (when
 the result contains :class:`bytes`
 data). The signatures of these methods match those of the corresponding
 :class:`str` and :class:`bytes` methods (except that the default encoding
 is ``'ascii'`` rather than ``'utf-8'``). Each produces a value of a
 corresponding type that contains either :class:`bytes` data (for
-:meth:`encode <DefragResult.encode>` methods) or :class:`str` data (for
-:meth:`decode <DefragResultBytes.decode>` methods).
+:meth:`~DefragResult.encode` methods) or :class:`str` data (for
+:meth:`~DefragResultBytes.decode` methods).
 
 Applications that need to operate on potentially improperly quoted URLs
 that may contain non-ASCII data will need to do their own decoding from
@@ -546,17 +546,17 @@ These subclasses add the attributes listed in the documentation for
 those functions, the encoding and decoding support described in the
 previous section, as well as additional methods:
 
-.. |split-scheme| replace:: :attr:`scheme <SplitResult.scheme>`
-.. |split-netloc| replace:: :attr:`netloc <SplitResult.netloc>`
-.. |split-path| replace:: :attr:`path <SplitResult.path>`
-.. |split-query| replace:: :attr:`query <SplitResult.query>`
-.. |split-frag| replace:: :attr:`fragment <SplitResult.fragment>`
-.. |split-username| replace:: :attr:`username <SplitResult.username>`
-.. |split-password| replace:: :attr:`password <SplitResult.password>`
-.. |split-hostname| replace:: :attr:`hostname <SplitResult.hostname>`
-.. |split-port| replace:: :attr:`port <SplitResult.port>`
-.. |defrag-url| replace:: :attr:`url <DefragResult.url>`
-.. |defrag-frag| replace:: :attr:`fragment <DefragResult.fragment>`
+.. |split-scheme| replace:: :attr:`~SplitResult.scheme`
+.. |split-netloc| replace:: :attr:`~SplitResult.netloc`
+.. |split-path| replace:: :attr:`~SplitResult.path`
+.. |split-query| replace:: :attr:`~SplitResult.query`
+.. |split-frag| replace:: :attr:`~SplitResult.fragment`
+.. |split-username| replace:: :attr:`~SplitResult.username`
+.. |split-password| replace:: :attr:`~SplitResult.password`
+.. |split-hostname| replace:: :attr:`~SplitResult.hostname`
+.. |split-port| replace:: :attr:`~SplitResult.port`
+.. |defrag-url| replace:: :attr:`~DefragResult.url`
+.. |defrag-frag| replace:: :attr:`~DefragResult.fragment`
 
 .. method:: SplitResult._replace(**kwargs)
 

Doc/library/urllib.request.rst

@@ -361,13 +361,10 @@ The following classes are provided:
 
    .. envvar:: no_proxy
 
-      A comma-separated list of hostname suffixes, optionally with ``:port``
-      appended, which shouldn't be reached via proxy.
-
-   The :envvar:`no_proxy` environment variable can be used to specify hosts
-   which shouldn't be reached via proxy; if set, it should be a comma-separated
-   list of hostname suffixes, optionally with ``:port`` appended, for example
-   ``cern.ch,ncsa.uiuc.edu,some.host:8080``.
+      This variable can be used to specify hosts which shouldn't be reached via
+      proxy; if set, it should be a comma-separated list of hostname suffixes,
+      optionally with ``:port`` appended, for example
+      ``cern.ch,ncsa.uiuc.edu,some.host:8080``.
 
    .. note::
 
@@ -673,38 +670,38 @@ OpenerDirector Objects
    *handler* should be an instance of :class:`BaseHandler`.  The following methods
    are searched, and added to the possible chains (note that HTTP errors are a
    special case).  Note that, in the following, *protocol* should be replaced
-   with the actual protocol to handle, for example ``http_response`` would be
-   the :ref:`protocol response handler <protocol_response>`.  Also *type*
-   should be replaced with the actual HTTP code, for example
-   ``http_error_404`` would handle HTTP 404 errors as described by the
-   :ref:`HTTP error handler pattern <http_error_nnn>`.
+   with the actual protocol to handle, for example :meth:`!http_response` would
+   be the HTTP protocol response handler.  Also *type* should be replaced with
+   the actual HTTP code, for example :meth:`!http_error_404` would handle HTTP
+   404 errors.
 
-   * ``<protocol>_open`` --- signal that the handler knows how to open
-     *protocol* URLs.
+   * :meth:`!<protocol>_open` --- signal that the handler knows how to open *protocol*
+     URLs.
 
-     See :ref:`the protocol open method pattern <protocol_open>` for more
-     information.
+     See |protocol_open|_ for more information.
 
-   * ``http_error_<type>`` --- signal that the handler knows how to handle HTTP
+   * :meth:`!http_error_\<type\>` --- signal that the handler knows how to handle HTTP
      errors with HTTP error code *type*.
 
-     See :ref:`the HTTP error handler pattern <http_error_nnn>` for more
-     information.
+     See |http_error_nnn|_ for more information.
 
-   * ``<protocol>_error`` --- signal that the handler knows how to handle errors
+   * :meth:`!<protocol>_error` --- signal that the handler knows how to handle errors
      from (non-\ ``http``) *protocol*.
 
-   * ``<protocol>_request`` --- signal that the handler knows how to pre-process
+   * :meth:`!<protocol>_request` --- signal that the handler knows how to pre-process
      *protocol* requests.
 
-     See :ref:`the protocol request method pattern <protocol_request>` for more
-     information.
+     See |protocol_request|_ for more information.
 
-   * ``<protocol>_response`` --- signal that the handler knows how to
+   * :meth:`!<protocol>_response` --- signal that the handler knows how to
      post-process *protocol* responses.
 
-     See :ref:`the protocol response method pattern <protocol_response>` for
-     more information.
+     See |protocol_response|_ for more information.
+
+.. |protocol_open| replace:: :meth:`!BaseHandler.<protocol>_open`
+.. |http_error_nnn| replace:: :meth:`!BaseHandler.http_error_\<nnn\>`
+.. |protocol_request| replace:: :meth:`!BaseHandler.<protocol>_request`
+.. |protocol_response| replace:: :meth:`!BaseHandler.<protocol>_response`
 
 .. method:: OpenerDirector.open(url, data=None[, timeout])