Lines Matching refs:egg
281 project's contents for possible problems each time it builds an egg.
326 the egg's metadata for use by tools like EasyInstall to use when installing
327 an ``.egg`` file.
334 may be distributed separately. The egg runtime system can automatically
521 Occasionally, there are situations where it's desirable to make an ``.egg``
537 invoking the egg with ``/bin/sh``, or by enabling execute permissions on the
538 ``.egg`` file. For the executable prelude to run, the appropriate version of
540 "long" name. That is, if the egg is built for Python 2.3, there must be a
551 error if the ``.egg`` file has been renamed or is invoked via a symlink that
626 - an egg, in the standard distutils ``sdist`` format,
645 must include an ``"#egg=project-version"`` suffix to the URL, to give a project
649 as an egg.
651 In the case of a VCS checkout, you should also append ``#egg=project-version``
663 ``vcs+proto://host/path@revision#egg=project-version``
893 ``package_name.egg-info/SOURCES.txt`` file, so make sure that this is removed if
978 bundled inside the egg file or directory, alongside the Python modules and
1119 developers include additional files in their ``ProjectName.egg-info``
1152 install anything. Instead, it creates a special ``.egg-link`` file in the
1159 If you have enabled the ``use_2to3`` flag, then of course the ``.egg-link``
1219 source or egg distributions respectively. Your project's current version must
1222 bdist_egg upload`` will register the package, build source and egg
1386 metadata. The argument should list the namespace packages that the egg
1416 projects are installed as ``.egg`` files, it will not work when the projects
1463 egg distributions by adding one or more of the following to the project's
1490 setup.py egg_info -rbDEV bdist_egg rotate -m.egg -k3
1492 to build an egg whose version info includes 'DEV-rNNNN' (where NNNN is the
1494 delete any egg files from the distribution directory except for the three
1528 project's ``.egg-info`` directory, out of the way of your main project
1569 .egg, .egg.zip, .tar.bz2, or .exe file, or if it has an ``#egg=project`` or
1570 ``#egg=project-version`` fragment identifier attached to it. EasyInstall
1580 ``#egg=project`` or ``#egg=project-version`` added to the URL. You should
1581 replace ``project`` and ``version`` with the values they would have in an egg
1582 filename. (Be sure to actually generate an egg and then use the initial part
1588 downloading unless it has a version included in the ``#egg=`` suffix, and
1593 "dev" (i.e., ``#egg=projectname-dev``), so that users can do something like
1690 setup.py daily bdist_egg # generate a daily-build .egg file
1703 setup.py alias bdist_egg bdist_egg rotate -k1 -m.egg
1706 command afterwards to delete all but the newest egg file. It doesn't loop
1732 This command generates a Python Egg (``.egg`` file) for the project. Python
1738 automatically discovered by the egg runtime system.
1741 the project's metadata (``.egg-info``) directory. If you have added any extra
1742 metadata files to the ``.egg-info`` directory, those files will be included in
1743 the new egg file's metadata directory, for use by the egg runtime system or by
1751 Set the directory where the ``.egg`` file will be placed. If you don't
1757 Set the platform name string that will be embedded in the egg's filename
1758 (assuming the egg contains C extensions). This can be used to override
1760 in mind, however, that the egg runtime system expects to see eggs with
1768 Don't include any modules' ``.py`` files in the egg, just compiled Python,
1787 ``.egg`` file.
1791 contents of this directory are zipped to create the ``.egg`` file, after
1811 The ``develop`` command works by creating an ``.egg-link`` file (named for the
1845 option to designate the staging area. The created ``.egg-link`` file will
1901 ``--egg-path=DIR``
1902 Force the generated ``.egg-link`` file to use a specified relative path
1938 ``egg_info`` - Create egg metadata and set build tags
1941 This command performs two operations: it updates a project's ``.egg-info``
1948 executing other commands. (It also generates the``.egg-info/SOURCES.txt``
1951 In addition to writing the core egg metadata defined by ``setuptools`` and
1999 location of the project's ``.egg-info`` directory. Commands that need to find
2006 ``--egg-base=SOURCEDIR, -e SOURCEDIR``
2007 Specify the directory that should contain the .egg-info directory. This
2019 Creating a dated "nightly build" snapshot egg::
2044 installation, with the addition of an ``.egg-info`` directory so that the
2056 ``install_egg_info`` - Install an ``.egg-info`` directory in ``site-packages``
2066 The parent directory where the ``.egg-info`` directory will be placed.
2073 command and use its options to locate the project's source ``.egg-info``
2092 you will use a glob pattern like ``.zip`` or ``.egg`` to match files of
2115 setup.py rotate --match=-py2.3*.egg,-py2.4*.egg --keep=1
2272 ``upload`` - Upload source and/or egg distributions to PyPI