Lines Matching refs:egg_info
246 * The `egg_info`_ command
1473 You can add these tags by adding ``egg_info`` and the desired options to
1476 `egg_info`_ command for more details.
1490 setup.py egg_info -rbDEV bdist_egg rotate -m.egg -k3
1614 python setup.py egg_info -Db "" sdist bdist_egg register upload
1616 The first part of this command (``egg_info -Db ""``) will override the
1625 python setup.py alias -u release egg_info -Db ""
1632 See the sections below on the `egg_info`_ and `alias`_ commands for more ideas.
1673 the distributions in different places, or use different ``egg_info`` tagging
1682 a sitewide alias called "daily", that sets various ``egg_info`` tagging
1685 setup.py alias --global-config daily egg_info --tag-build=development
1695 ``egg_info --tag-build=development``.
1740 This command runs the `egg_info`_ command (if it hasn't already run) to update
1825 up-to-date, and the ``egg_info`` command to ensure the project's metadata is
1938 ``egg_info`` - Create egg metadata and set build tags
1953 metadata files as well, by defining entry points in the ``egg_info.writers``
1980 to the ``egg_info`` command.
2003 Other ``egg_info`` Options
2016 ``egg_info`` Examples
2021 python setup.py egg_info --tag-date --tag-build=DEV bdist_egg
2026 python setup.py egg_info -RDb "" sdist bdist_egg register upload
2028 (Notice that ``egg_info`` must always appear on the command line *before* any
2071 This command assumes that the ``egg_info`` command has been given valid options
2072 via the command line or ``setup.cfg``, as it will invoke the ``egg_info``
2230 ``egg_info`` to ensure that any C extensions and project metadata are
2623 file when the ``egg_info`` command is run.
2625 The ``egg_info`` command looks for extension points in an ``egg_info.writers``
2637 "egg_info.writers": [
2638 "foo_bar.txt = setuptools.command.egg_info:write_arg",
2655 As you can see, ``egg_info.writers`` entry points must be a function taking
2656 three arguments: a ``egg_info`` command instance, the basename of the file to