Lines Matching refs:egg

24 of multiple versions) rely specifically on the "egg" format (either as a
26 work correctly so long as "egg-info" metadata directories are available for
35 an installed egg can be *automatically* found and added to ``sys.path`` in
90     and egg links.  Built eggs are directories or zipfiles whose name ends
91     with ``.egg`` and follows the egg naming conventions, and contain an
93     normal directories of Python code with one or more ``ProjectName.egg-info``
94     subdirectories. The development egg format is also used to provide a
97     are ``*.egg-link`` files that contain the name of a built or
98     development egg, to support symbolic linking on platforms that do not
168     called for you when an egg is automatically added to ``sys.path``, but if
443    An attempt is made to resolve each egg's dependencies. If the attempt is
444    successful, the egg and its dependencies are added to the output list and to
903     `basename` is a string naming the distribution, like ``Foo-1.2-py2.4.egg``.
904     If `basename` ends with ``.egg``, then the project's name, version, python
992     "System" and "Development" eggs (i.e., ones that use the ``.egg-info``
1034     the ".egg" extension.  For example, a distribution for project "Foo"
1038     them back when parsing a ".egg" file name.)
1177     egg), it will be extracted to a cache directory, and the filename within
1235     enclosing egg (which may not be the name of the enclosing zipfile!),
1236     including its ".egg" extension.  `names`, if provided, should be a
1237     sequence of path name parts "under" the egg's extraction location.
1292     work when the named package is in an ``.egg`` file or directory, but
1481     This provider class adds in some egg-specific features that are common
1506     "unpacked egg", and a ``ProjectName.egg-info`` subdirectory of `path` for
1507     a "development egg".  However, other uses are possible for custom purposes.
1512     represent a "basket" (a zipfile containing multiple ".egg" subdirectories)
1513     a specific egg *within* a basket, or a zipfile egg (where the zipfile
1514     itself is a ".egg").  It can also be a combination, such as a zipfile egg
1522     designated file.  (This provider is used to wrap ``.egg-info`` files
1613     filename (or ``#egg=name-version`` tag) without ambiguity.  You
1688    ``site-packages`` would take precedence over ``.egg`` files (or directories)
1694  * Allow ``.egg-link`` files to contain relative paths.
1735    versions for safe use in constructing egg filenames from a Distribution
1742    eggs using ``.egg-info`` format.
1749  * Added support for ``.egg-info`` files or directories with version/platform
1752    system-installed egg, without needing to use ``.egg`` directories, zipfiles,
1791  * Fixed a problem extracting zipped files on Windows, when the egg in question
1822      an egg).
1880  * Fixed a bug in resource extraction from nested packages in a zipped egg.
1892    ``sys.path`` (e.g. if a user deletes an egg without removing it from the
1895  * Fix a problem with "basket" support in ``pkg_resources``, where egg-finding
1896    never actually went inside ``.egg`` files.
1930  * ``pkg_resources`` now supports "egg baskets" -- .egg zipfiles which contain
1931    multiple distributions in subdirectories whose names end with ``.egg``.