Lines Matching refs:find_spec

278     pair: finder; find_spec
284 :meth:`~importlib.abc.MetaPathFinder.find_spec()` which takes three arguments:
295 The :meth:`~importlib.abc.MetaPathFinder.find_spec()` method of meta path
309 ``mpf.find_spec("foo", None, None)`` on each meta path finder (``mpf``). After
312 ``mpf.find_spec("foo.bar", foo.__path__, None)``. Once ``foo.bar`` has been
314 ``mpf.find_spec("foo.bar.baz", foo.bar.__path__, None)``.
326    The :meth:`~importlib.abc.MetaPathFinder.find_spec` method of meta path
330    ``find_spec()``.
427 :meth:`~importlib.abc.MetaPathFinder.find_spec` method would just return a
784 :meth:`~importlib.abc.MetaPathFinder.find_spec` protocol previously
806 based finder's :meth:`~importlib.machinery.PathFinder.find_spec` method as
808 :meth:`~importlib.machinery.PathFinder.find_spec` is given, it will be a
842 :meth:`~importlib.machinery.PathFinder.find_spec` method will store ``None``
858 :meth:`importlib.machinery.PathFinder.find_spec` will be the actual current
866 the :meth:`~importlib.abc.PathEntryFinder.find_spec` method.
868 :meth:`~importlib.abc.PathEntryFinder.find_spec` takes two arguments: the
870 module.  ``find_spec()`` returns a fully populated spec for the module.
878    :meth:`~importlib.abc.PathEntryFinder.find_spec` replaced
881    are now deprecated, but will be used if ``find_spec()`` is not defined.
884    instead of ``find_spec()``.  The methods are still respected for the
885    sake of backward compatibility.  However, if ``find_spec()`` is
928 :meth:`~importlib.abc.MetaPathFinder.find_spec` instead of returning