Lines Matching refs:__path__

82 module.  Specifically, any module that contains a ``__path__`` attribute is
141 Namespace packages do not use an ordinary list for their ``__path__``
268 ``package.__path__``) processing, at the point where their associated path
301 ``__path__`` attribute. If the appropriate ``__path__`` attribute cannot
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)``.
592 .. attribute:: __path__
595    object's ``__path__`` attribute must be set.  The value must be
596    iterable, but may be empty if ``__path__`` has no further significance.
597    If ``__path__`` is not empty, it must produce strings when iterated
598    over. More details on the semantics of ``__path__`` are given
601    Non-package modules should not have a ``__path__`` attribute.
624 module.__path__
627 By definition, if a module has a ``__path__`` attribute, it is a package.
629 A package's ``__path__`` attribute is used during imports of its subpackages.
632 However, ``__path__`` is typically much more constrained than
635 ``__path__`` must be an iterable of strings, but it may be empty.
637 ``__path__``, and :data:`sys.path_hooks` (described below) are
638 consulted when traversing a package's ``__path__``.
640 A package's ``__init__.py`` file may set or alter the package's ``__path__``
643 longer need to supply ``__init__.py`` files containing only ``__path__``
644 manipulation code; the import machinery automatically sets ``__path__``
789 :data:`sys.path_hooks` and :data:`sys.path_importer_cache`.  The ``__path__``
809 list of string paths to traverse - typically a package's ``__path__``