Lines Matching +full:unmanaged +full:- +full:versions +full:- +full:check
8 provides runtime support for using C extensions that are inside zipfile-format
9 eggs, support for merging packages that have separately-distributed modules or
14 `importlib.resources <https://docs.python.org/3/library/importlib.html#module-importlib.resources>`…
21 --------
23 --------
28 of multiple versions) rely specifically on the "egg" format (either as a
30 work correctly so long as "egg-info" metadata directories are available for
41 docutils' PDF support". This feature allows mutually conflicting versions of
42 a distribution to co-exist in the same Python installation, with individual
96 ``EGG-INFO`` subdirectory (zipped or otherwise). Development eggs are
97 normal directories of Python code with one or more ``ProjectName.egg-info``
100 doesn't use ``pkg_resources`` to request specific versions. Egg links
101 are ``*.egg-link`` files that contain the name of a built or
109 .. _architectural overview: http://mail.python.org/pipermail/distutils-sig/2005-June/004652.html
112 .. -----------------
114 .. -----------------
132 .. For now, please check out the extensive `API Reference`_ below.
135 -------------
137 -------------
144 multiple, separately-packaged distributions. They are normally used to split
216 version conflicts for applications which require non-default versions of
227 ----------------------------
229 The following methods of ``WorkingSet`` objects are also available as module-
238 ``requirements`` must be a string or a (possibly-nested) sequence
239 thereof, specifying the distributions and versions required. The
248 directly. It's intended more for use in quick-and-dirty scripting and
295 -------------------------------------
319 Yield distributions for non-duplicate projects in the working set.
339 requirement that cannot be met by an already-installed distribution; it
361 debugging. If you are experiencing import problems, you should check
373 ------------------------------
376 a new distribution (such as a plug-in component) has been added to a working
383 already-active distributions, you do not need to loop over the working set
399 ----------------
422 contains all currently-available distributions.
428 This method returns a 2-tuple: (``distributions``, ``error_info``), where
461 revert to a known-good configuration. (That is, they may wish to revert to
462 a known configuration if the ``error_info`` return value is non-empty.)
466 projects named "AaronsPlugin" and "ZekesPlugin" both need different versions
486 that platform-specific distributions must be compatible with. If
489 it defaults to the currently-running version.
513 been added. (i.e., adding the same distribution more than once is a no-op.)
531 in-place addition (``+=``) instead.
535 *in-place*, updating the existing instance and returning it. The
575 ``Requirement`` objects express what versions of a project are suitable for
582 --------------------
611 function. For example, if the hypothetical "Report-O-Rama" project offered
613 provide that support. Thus, a project needing Report-O-Rama's PDF features
614 could use a requirement of ``Report-O-Rama[PDF]`` to request installation
615 or activation of both Report-O-Rama and any libraries it needs in order to
618 pip install Report-O-Rama[PDF]
621 ``pkg_resources.require('Report-O-Rama[PDF]')`` to add the necessary
625 should be installed -- the requirement will be installed if the marker
631 --------------------------------------
639 assumed to be an already-parsed version.
643 versions are acceptable. Adjacent redundant conditions are effectively
645 ``"<2,<3"`` produces the same results as ``"<2"``). ``"!="`` versions are
651 case-insensitively equal project names, version specifiers, and "extras".
664 An all-lowercase version of the ``project_name``, useful for comparison
669 be all-lowercase and normalized using the ``safe_extra()`` parsing utility
674 A list of ``(op,version)`` tuples, sorted in ascending parsed-version
703 framework that offers various pre- or post-publishing hooks might define an
726 ---------------
773 --------------------
821 sequence of lines, it is first split into .ini-style sections (using
829 ----------------------
870 ---------------------------------
876 objects from one of these high-level APIs:
907 ``basename`` is a string naming the distribution, like ``Foo-1.2-py2.4.egg``.
933 ---------------------------
938 make it actively importable. For non-importable distributions, this is
950 case-insensitive comparison and indexing of distributions by project name.
963 ``Distribution`` to try to discover its version by reading its ``PKG-INFO``
964 metadata file. If ``PKG-INFO`` is unavailable or can't be parsed,
983 ``None`` if the distribution is "pure Python" and therefore cross-platform.
996 "System" and "Development" eggs (i.e., ones that use the ``.egg-info``
1002 ------------------------
1040 of ``Foo-1.2-py2.3-win32``. Any dashes in the name or version are
1105 and makes most of its methods available as top-level names in the
1117 ---------------------
1136 segment will be treated as a peer of the top-level modules or packages in the
1139 Note that resource names must be ``/``-separated paths rooted at the package,
1148 Return a readable file-like object for the specified resource; it may be
1151 will be read as-is.
1175 -------------------
1180 use this method (or module-level function) to obtain a filename for a
1198 platform-specific fallbacks. See that routine's documentation for more
1225 --------------------
1232 *not* available as top-level functions tied to the global ``ResourceManager``;
1257 Perform any platform-specific postprocessing of ``tempname``.
1274 metadata resource names are ``/``-separated and should not contain ``..`` or
1293 and "single-version externally-managed" packages do not have any way to
1303 -----------------------------
1322 Yield named metadata resource as list of non-blank non-comment lines. This
1350 directly for miscellaneous requirement-resolution problems like trying to
1357 The requested version of a project conflicts with an already-activated
1383 with other (PEP 302-compatible) importers or module loaders, you may need to
1425 -----------------
1441 Return a readable file-like object for ``resource_name``.
1455 ``os.listdir()``. Requesting the contents of a non-existent directory may
1461 You may instead wish to subclass one of the `built-in resource providers`_.
1464 Built-in Resource Providers
1465 ---------------------------
1486 This provider class adds in some egg-specific features that are common
1507 Create an ``IResourceProvider`` for a filesystem-based distribution, where
1510 ``egg_info`` should usually be the ``EGG-INFO`` subdirectory of ``path`` for an
1511 "unpacked egg", and a ``ProjectName.egg-info`` subdirectory of ``path`` for
1515 Create an ``IResourceProvider`` for a zipfile-based distribution. The
1524 resource: ``PKG-INFO``. The supplied path should be a distutils PKG-INFO
1526 requests for ``PKG-INFO`` will be answered using the contents of the
1527 designated file. (This provider is used to wrap ``.egg-info`` files
1528 installed by vendor-supplied system packages.)
1534 In addition to its high-level APIs, ``pkg_resources`` also includes several
1535 generally-useful utility routines. These routines are used to implement the
1536 high-level APIs, but can also be quite useful by themselves.
1540 -----------------
1548 invalid versions will continue sorting using the original algorithm.
1553 Yield non-empty/non-comment lines from a string/unicode or a possibly-
1555 is split into lines, and each non-blank, non-comment line is yielded after
1556 stripping leading and trailing whitespace. (Lines whose first non-blank
1575 Split a string (or possibly-nested iterable thereof), yielding ``(section,
1576 content)`` pairs found using an ``.ini``-like syntax. Each ``section`` is
1577 a whitespace-stripped version of the section name ("``[section]``")
1579 comment-only lines. If there are any non-blank, non-comment lines before
1596 All non-alphanumeric runs are condensed to single "-" characters, such that
1597 a name like "The $$$ Tree" becomes "The-Tree". Note that if you are
1599 ``to_filename()`` so all dashes ("-") are replaced by underscores ("_").
1607 generating a filename from this you should replace any "-" characters in
1613 similar to ``safe_name()`` except that non-alphanumeric runs are replaced
1617 Escape a name or version string so it can be used in a dash-separated
1618 filename (or ``#egg=name-version`` tag) without ambiguity. You
1624 ------------------
1629 ``"macosx-10.4-ppc"``. All other platforms return the same uname-based
1632 on the local machine. (Backward compatibility note: setuptools versions
1647 compatible, and ``True`` is returned. Currently, the only non-equal
1656 if set. Otherwise, on Windows, it returns a "Python-Eggs" subdirectory of
1658 ``os.path.expanduser("~/.python-eggs")`` if ``PYTHON_EGG_CACHE`` is not
1663 -----------------
1670 -------------------
1682 reflect the platform's case-sensitivity, so there is always the possibility
1683 of two apparently-different paths being equal on such platforms.
1686 -------
1692 * Fix package precedence problem where single-version eggs installed in
1693 ``site-packages`` would take precedence over ``.egg`` files (or directories)
1694 installed in ``site-packages``.
1699 * Allow ``.egg-link`` files to contain relative paths.
1705 * Fix "dev" versions being considered newer than release candidates.
1712 case-insensitive filesystems possibly not showing up in the default
1716 * Fixed a duplicate path insertion problem on case-insensitive filesystems.
1728 cache permission problems get a more user-friendly explanation of the
1740 versions for safe use in constructing egg filenames from a Distribution
1747 eggs using ``.egg-info`` format.
1754 * Added support for ``.egg-info`` files or directories with version/platform
1756 option of including ``PKG-INFO`` files to indicate the presence of a
1757 system-installed egg, without needing to use ``.egg`` directories, zipfiles,
1760 * Changed ``parse_version()`` to remove dashes before pre-release tags, so
1761 that ``0.2-rc1`` is considered an *older* version than ``0.2``, and is equal
1762 to ``0.2rc1``. The idea that a dash *always* meant a post-release version
1763 was highly non-intuitive to setuptools users and Python developers, who
1764 seem to want to use ``-rc`` version numbers a lot.
1776 * Fix path insertion algorithm for case-insensitive filesystems.
1784 This allows e.g. eggs in ``site-packages`` to override unmanaged modules in
1789 non-namespace modules have already been imported and issues a warning if
1792 * Changed dependency processing so that it's breadth-first, allowing a
1812 ``zipimport``, and the previously-broken "eager resource" support.
1826 place of the package name (to allow access to non-package data files in
1835 path will be module-relative, rather than relative to the distribution's
1854 create a distribution with an un-normalized filesystem path.
1865 that tells it to only yield distributions whose location is the passed-in
1888 * Updated extraction/cache mechanism for zipped resources to avoid inter-
1889 process and inter-thread races during extraction. The default cache
1891 and the default Windows cache is now a ``Python-Eggs`` subdirectory of the
1896 * Fix a problem with ``pkg_resources`` being confused by non-existent eggs on
1898 ``easy-install.pth`` file).
1900 * Fix a problem with "basket" support in ``pkg_resources``, where egg-finding
1924 * Fixed a bug in requirements processing for exact versions (i.e. ``==`` and
1928 arbitrary distribution names and versions found on PyPI.
1935 * ``pkg_resources`` now supports "egg baskets" -- .egg zipfiles which contain