Lines Matching full:setuptools

4 Configuring setuptools using ``pyproject.toml`` files
12    ``setuptools`` via ``pyproject.toml`` files is still experimental and might
23        from setuptools import setup
29 ``Setuptools`` has adopted this standard and will use the information contained
33 be used with ``setuptools``. It contains two TOML tables (identified by the
36 :pypi:`build` or :pypi:`pip`) to use ``setuptools`` and any other plugins (e.g.
37 ``setuptools-scm``) to build the package.
46    requires = ["setuptools", "setuptools-scm"]
47    build-backend = "setuptools.build_meta"
75 Setuptools-specific configuration
80 ``setuptools``-specific configurations that can be set by users that require
85 file, and can be set via the ``tool.setuptools`` table:
91 ``zip-safe``              boolean                     If not specified, ``setuptools`` will try to …
121    ``setuptools`` will attempt to perform :ref:`auto-discovery`, which should
132       [tool.setuptools.packages.find]
147       [tool.setuptools]
158 ``setuptools`` itself or the plugins installed via ``build-system.requires``
159 (e.g. ``setuptools-scm`` is capable of deriving the current project version
165 When these fields are expected to be provided by ``setuptools`` a
166 corresponding entry is required in the ``tool.setuptools.dynamic`` table
176    [tool.setuptools.dynamic]
200    When resolving these metadata keys, ``setuptools`` will look for
206    values that are interpreted differently by ``setuptools`` (usually triggering an
210    directive for ``tool.setuptools.packages``, or ``{attr = "mymodule.attr"}``
211    directive for ``tool.setuptools.dynamic.version``.