Lines Matching full:setup

41 Setuptools currently supports configurations from either ``setup.cfg``,
42 ``setup.py`` or ``pyproject.toml`` [#experimental]_ files, however, configuring new
43 projects via ``setup.py`` is discouraged [#setup.py]_.
47 .. tab:: setup.cfg
63 .. tab:: setup.py [#setup.py]_
67         from setuptools import setup
69         setup(
99         setup.cfg # or setup.py
112 more information to your setup script to help people find or learn about your
122 the ``packages`` keyword in ``setup.cfg``.  However, for very large projects,
127 .. tab:: setup.cfg
141 .. tab:: setup.py [#setup.py]_
147         setup(
177 setup also allows you to adopt a ``src/`` layout. For more details and advanced
199 .. tab:: setup.cfg
207 .. tab:: setup.py [#setup.py]_
211         setup(
241 .. tab:: setup.cfg
250 .. tab:: setup.py [#setup.py]_
254         setup(
294 .. tab:: setup.cfg
301 .. tab:: setup.py [#setup.py]_
305         setup(
344     Prior to :ref:`pip v21.1 <pip:v21-1>`, a ``setup.py`` script was
346     versions of pip, ``setup.cfg``-only projects may be installed in this mode.
350     ``setup.py`` file in file in your repository if you want to use editable
357         from setuptools import setup
359         setup()
361     You can still keep all the configuration in :doc:`setup.cfg </userguide/declarative_config>`
373 Transitioning from ``setup.py`` to ``setup.cfg``
376 into a full-fledged ``setup.cfg`` to declare your package information instead
377 of running ``setup()``. This inevitably brings challenges due to a different
379 understanding how ``setup.cfg`` is parsed by ``setuptools`` to ease the pain of
399 .. [#setup.py]
400    The ``setup.py`` file should be used only when custom scripting during the
403    contributing to existing packages that use ``setup.py``.
405    :doc:`setup.cfg <declarative_config>` or :doc:`pyproject.toml
406    <pyproject_config>` and use ``setup.py`` only for the parts not