Lines Matching refs:find_spec

276     pair: finder; find_spec
282 :meth:`~importlib.abc.MetaPathFinder.find_spec()` which takes three arguments:
293 The :meth:`~importlib.abc.MetaPathFinder.find_spec()` method of meta path
307 ``mpf.find_spec("foo", None, None)`` on each meta path finder (``mpf``). After
310 ``mpf.find_spec("foo.bar", foo.__path__, None)``. Once ``foo.bar`` has been
312 ``mpf.find_spec("foo.bar.baz", foo.bar.__path__, None)``.
324    The :meth:`~importlib.abc.MetaPathFinder.find_spec` method of meta path
328    ``find_spec()``.
422 :meth:`~importlib.abc.MetaPathFinder.find_spec` method would just return a
769 :meth:`~importlib.abc.MetaPathFinder.find_spec` protocol previously
791 based finder's :meth:`~importlib.machinery.PathFinder.find_spec` method as
793 :meth:`~importlib.machinery.PathFinder.find_spec` is given, it will be a
827 :meth:`~importlib.machinery.PathFinder.find_spec` method will store ``None``
843 :meth:`importlib.machinery.PathFinder.find_spec` will be the actual current
851 the :meth:`~importlib.abc.PathEntryFinder.find_spec` method.
853 :meth:`~importlib.abc.PathEntryFinder.find_spec` takes two argument, the
855 module.  ``find_spec()`` returns a fully populated spec for the module.
864    :meth:`~importlib.abc.PathEntryFinder.find_spec` replaced
867    are now deprecated, but will be used if ``find_spec()`` is not defined.
870    instead of ``find_spec()``.  The methods are still respected for the
871    sake of backward compatibility.  However, if ``find_spec()`` is
920 :meth:`~importlib.abc.MetaPathFinder.find_spec` instead of returning