latest--partial-setuptools

Package and virtual package names contained within this package (not supported by pip)

Packages which this package renders obsolete (not supported by pip)

Whether the project can be safely installed and run from a zip file. OBSOLETE: only relevant for pkg_resources, easy_install and setup.py install in the context of eggs (DEPRECATED).

Legacy way of defining scripts (entry-points are preferred). Equivalent to the script keyword in setup.py (it was renamed to avoid confusion with entry-point based project.scripts defined in :pep:621). DISCOURAGED: generic script wrappers are tricky and may not work properly. Whenever possible, please use project.scripts instead.

Resources that should be extracted together, if any of them is needed, or if any C extensions included in the project are imported. OBSOLETE: only relevant for pkg_resources, easy_install and setup.py install in the context of eggs (DEPRECATED).

Packages that should be included in the distribution. It can be given either as a list of package identifiers or as a dict-like structure with a single key find which corresponds to a dynamic call to setuptools.config.expand.find_packages function. The find key is associated with a nested dict-like structure that can contain where, include, exclude and namespaces keys, mimicking the keyword arguments of the associated function.

:class:dict-like structure mapping from package names to directories where their code can be found. The empty string (as key) means that all packages are contained inside the given directory will be included in the distribution.

Mapping from package names to lists of glob patterns. Usually this option is not needed when using include-package-data = true For more information on how to include data files, check setuptools docs <https://setuptools.pypa.io/en/latest/userguide/datafiles.html>_.

Automatically include any data files inside the package directories that are specified by MANIFEST.in For more information on how to include data files, check setuptools docs <https://setuptools.pypa.io/en/latest/userguide/datafiles.html>_.

Mapping from package names to lists of glob patterns that should be excluded For more information on how to include data files, check setuptools docs <https://setuptools.pypa.io/en/latest/userguide/datafiles.html>_.

DEPRECATED: use implicit namespaces instead (:pep:420).

Modules that setuptools will manipulate

dict-like structure where each key represents a directory and the value is a list of glob patterns that should be installed in them. DISCOURAGED: please notice this might not work as expected with wheels. Whenever possible, consider using data files inside the package directories (or create a new namespace package that only contains data files). See data files support <https://setuptools.pypa.io/en/latest/userguide/datafiles.html>_.

Mapping of distutils-style command names to setuptools.Command subclasses which in turn should be represented by strings with a qualified class name (i.e., "dotted" form with module), e.g.::

 cmdclass = {mycmd = "pkg.subpkg.module.CommandClass"}

The command class should be a directly defined at the top-level of the containing module (no class nesting).

PROVISIONAL: list of glob patterns for all license files being distributed. (likely to become standard with :pep:639). By default: ['LICEN[CS]E*', 'COPYING*', 'NOTICE*', 'AUTHORS*']

Instructions for loading :pep:621-related metadata dynamically