Fix None references.
This commit is contained in:
parent
5998c3c5db
commit
e8108d36cd
|
@ -173,15 +173,15 @@ Impact on import finders and loaders
|
|||
|
||||
PEP 302 defines "finders" that are called to search path elements.
|
||||
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
|
||||
new ``find_loader(fullname)`` method. ``fullname`` has the same
|
||||
meaning as for ``find_module``. ``find_loader`` always returns a
|
||||
2-tuple of ``(loader, <iterable-of-path-entries>)``. ``loader`` may
|
||||
be None, in which case ``<iterable-of-path-entries>`` (which may be
|
||||
empty) is added to the list of recorded path entries and path
|
||||
searching continues. If ``loader`` is not None, it is immediately
|
||||
be ``None``, in which case ``<iterable-of-path-entries>`` (which may
|
||||
be empty) is added to the list of recorded path entries and path
|
||||
searching continues. If ``loader`` is not ``None``, it is immediately
|
||||
used to load a module or regular package.
|
||||
|
||||
Note that multiple path entries per finder are allowed. This is to
|
||||
|
|
Loading…
Reference in New Issue