From: Andrew Svetlov Date: Thu, 15 Nov 2012 14:28:21 +0000 (+0200) Subject: Issue #16144: Fix misleading sentence in reference/import. X-Git-Tag: v3.3.1rc1~634 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e2cf03e499c64fc51a46356169642add4890f33e;p=python Issue #16144: Fix misleading sentence in reference/import. Patch by Manuel Pégourié-Gonnard --- diff --git a/Doc/reference/import.rst b/Doc/reference/import.rst index 4688e78d15..fdecc76950 100644 --- a/Doc/reference/import.rst +++ b/Doc/reference/import.rst @@ -44,9 +44,9 @@ described in the sections below. .. versionchanged:: 3.3 The import system has been updated to fully implement the second phase - of PEP 302. There is no longer any implicit import machinery - the full + of :pep:`302`. There is no longer any implicit import machinery - the full import system is exposed through :data:`sys.meta_path`. In addition, - native namespace package support has been implemented (see PEP 420). + native namespace package support has been implemented (see :pep:`420`). :mod:`importlib` @@ -219,9 +219,9 @@ whatever strategy it knows about. Objects that implement both of these interfaces are referred to as :term:`importers ` - they return themselves when they find that they can load the requested module. -Python includes a number of default finders and importers. One -knows how to locate frozen modules, and another knows how to locate -built-in modules. A third default finder searches an :term:`import path` +Python includes a number of default finders and importers. The first one +knows how to locate built-in modules, and the second knows how to locate +frozen modules. A third default finder searches an :term:`import path` for modules. The :term:`import path` is a list of locations that may name file system paths or zip files. It can also be extended to search for any locatable resource, such as those identified by URLs.