Lines Matching refs:eggs

20 principle of Python eggs is that they should be discoverable and
22 easily and efficiently find out what eggs are present on a system, and
23 to ensure that the desired eggs' contents are importable.
25 There are two basic formats currently implemented for Python eggs:
65 egg -- there may be several eggs "scrambled" together in a single
92 If eggs contained only code and resources, there would of course be
102 The minimum project metadata that all eggs must have is a standard
105 this to be the only metadata file included, ``.egg-info`` format eggs
181 These files are not eggs, strictly speaking. They simply provide a way
196 searches for available eggs, ``.egg-link`` files are opened and the
201 more eggs.  That is, the name must either end in ``.egg``, or else it
202 should be the parent directory of one or more ``.egg-info`` format eggs.
209 to find the project's setup directory and build eggs or perform other setup
363 egg, after ensuring that sys.path includes the egg and any eggs it
439 installation time, but in more recent versions, setuptools installs eggs
457 Although this metadata is included with distributed eggs, it is not
465 included in distributed eggs, and it is possible that future versions of
596 directories, including all the fixups needed to ensure that eggs always
607 2. All eggs installed by EasyInstall in any ``.pth`` file in each
613 3. All eggs installed by EasyInstall in any ``.pth`` file in each "site"
620    eggs installed by EasyInstall, again following the same relative
627 ``sys.path``.  Sections 2 and 3 are inserted to support eggs, and
674 (``.egg-info`` eggs do not have script wrappers associated with them,
679 to installed eggs.  For example, an uninstallation tool could use this