Fix None references.

This commit is contained in:
Eric V. Smith 2012-05-15 21:53:01 -04:00
parent 5998c3c5db
commit e8108d36cd
1 changed files with 4 additions and 4 deletions

View File

@ -173,15 +173,15 @@ Impact on import finders and loaders
PEP 302 defines "finders" that are called to search path elements. PEP 302 defines "finders" that are called to search path elements.
These finders' ``find_module`` methods return either a "loader" object These finders' ``find_module`` methods return either a "loader" object
or None. or ``None``.
For a finder to contribute to namespace packages, it must implement a For a finder to contribute to namespace packages, it must implement a
new ``find_loader(fullname)`` method. ``fullname`` has the same new ``find_loader(fullname)`` method. ``fullname`` has the same
meaning as for ``find_module``. ``find_loader`` always returns a meaning as for ``find_module``. ``find_loader`` always returns a
2-tuple of ``(loader, <iterable-of-path-entries>)``. ``loader`` may 2-tuple of ``(loader, <iterable-of-path-entries>)``. ``loader`` may
be None, in which case ``<iterable-of-path-entries>`` (which may be be ``None``, in which case ``<iterable-of-path-entries>`` (which may
empty) is added to the list of recorded path entries and path be empty) is added to the list of recorded path entries and path
searching continues. If ``loader`` is not None, it is immediately searching continues. If ``loader`` is not ``None``, it is immediately
used to load a module or regular package. used to load a module or regular package.
Note that multiple path entries per finder are allowed. This is to Note that multiple path entries per finder are allowed. This is to