Lines Matching full:distributions
26 introspecting, activating and using installed Python distributions. Some
31 relevant distributions.
81 A collection of distributions potentially available for importing, but not
86 A collection of distributions actually available for importing, as on
92 Eggs are pluggable distributions in one of the three formats currently
118 Finding and Activating Package Distributions
144 multiple, separately-packaged distributions. They are normally used to split
157 contained packages and modules may be spread across multiple distributions.
159 corresponding package in all distributions on ``sys.path`` that contain a
187 distributions. In general, there is only one meaningful ``WorkingSet``
188 instance: the one that represents the distributions that are currently active
214 All distributions available directly on ``sys.path`` will be activated
217 those distributions. To handle this situation, ``pkg_resources`` checks for a
236 Ensure that distributions matching ``requirements`` are activated
239 thereof, specifying the distributions and versions required. The
240 return value is a sequence of the distributions that needed to be
241 activated to fulfill the requirements; all relevant distributions are
284 distributions in the working set, otherwise only ones matching both
286 distributions in the order that the distributions appear in the working
302 Add a path item to the ``entries``, finding any distributions on it. You
307 This method uses ``find_distributions(entry,True)`` to find distributions
319 Yield distributions for non-duplicate projects in the working set.
333 List all distributions needed to (recursively) meet ``requirements``
383 already-active distributions, you do not need to loop over the working set
408 Scan ``plugin_env`` and identify which distributions could be added to this
413 distributions, errors = working_set.find_plugins(
416 map(working_set.add, distributions) # add plugins+libs to sys.path
420 distributions that are in the project's "plugin directory" or directories.
422 contains all currently-available distributions.
426 every directory on ``sys.path`` will be scanned for distributions.
428 This method returns a 2-tuple: (``distributions``, ``error_info``), where
429 ``distributions`` is a list of the distributions found in ``plugin_env`` that
430 were loadable, along with any other distributions that are needed to resolve
432 distributions to an exception instance describing the error that occurred.
438 distributions to the working set so that they are available on sys.path.
443 the project names of the distributions present in ``plugin_env`` are sorted.
477 distributions during dependency resolution.
480 Create an environment snapshot by scanning ``search_path`` for distributions
486 that platform-specific distributions must be compatible with. If
492 wish to include *all* distributions, not just those compatible with the
495 Note that ``search_path`` is scanned immediately for distributions, and the
496 resulting ``Environment`` is a snapshot of the found distributions. It
498 installation or removal of distributions.
501 Returns a list of distributions for the given project name, ordered
503 for distributions that contain the same version of the project.) If there
504 are no distributions for the project, returns an empty list.
507 Yield the unique project names of the distributions in this environment.
525 a *new* environment object that contains all the distributions previously
527 ``python`` of ``None``, meaning that it will not reject any distributions
536 ``platform`` and ``python`` filter attributes take effect, so distributions
561 Scan ``search_path`` for distributions usable on ``platform``
563 Any distributions found are added to the environment. ``search_path`` should
565 supplied, ``sys.path`` is used. Only distributions conforming to
568 find the distributions from each item in ``search_path``, and then calling
577 ``pkg_resources`` APIs in order to find distributions that a script or
610 project, that may require additional project distributions in order to
622 distributions to sys.path at runtime.
688 Entry points are a simple way for distributions to "advertise" Python objects
689 (such as functions or classes) for use by other distributions. Extensible
691 or group, either from a specific distribution or from all active distributions
720 if multiple distributions advertise an entry point; some possibilities include
762 distributions in the working set on sys.path, otherwise only ones matching
764 the active distributions in the order that the distributions appear on
789 argument to find out what other distributions may need to be activated
845 will be used to search for needed distributions if they are not already
869 Getting or Creating Distributions
874 `Environment Objects`_, which are containers for active distributions and
875 available distributions, respectively.) You can also obtain ``Distribution``
879 Yield distributions accessible via ``path_item``. If ``only`` is true, yield
880 only distributions whose ``location`` is equal to ``path_item``. In other
881 words, if ``only`` is true, this yields any distributions that would be
883 also yields distributions that are "in" or "under" ``path_item``, but would
893 However, if you're creating specialized tools for working with distributions,
938 make it actively importable. For non-importable distributions, this is
950 case-insensitive comparison and indexing of distributions by project name.
971 distributions by version. (See the `Parsing Utilities`_ section below for
988 two distributions that have the same ``project_name`` and
994 only by the ``setuptools.package_index`` module, when sorting distributions
1011 merged with the contents provided by any other active distributions. See
1127 multiple distributions, and is therefore ambiguous as to which distribution
1387 Register ``distribution_finder`` to find distributions in ``sys.path`` items.
1631 This string is the minimum platform version required by distributions built
1782 * Activated distributions are now inserted in ``sys.path`` (and the working
1809 directory scanning for distributions.
1850 of the setuptools' code that generates distributions from the filesystem
1865 that tells it to only yield distributions whose location is the passed-in
1872 distributions for the named project.
1879 you register a callback for notifications about distributions added to
1880 ``sys.path`` (including the distributions already on it). This is
1882 search for plugin metadata in distributions added at runtime.
1936 multiple distributions in subdirectories whose names end with ``.egg``.