Lines Matching full:packages

29         packages =
39             packages=['mypkg1', 'mypkg2']
48         packages = ["mypkg1", "mypkg2"]
52 If your packages are not in the root of the repository you also need to
63             # directory containing all the packages (e.g.  src/mypkg1, src/mypkg2)
81             # directory containing all the packages (e.g.  src/mypkg1, src/mypkg2)
103             # directory containing all the packages (e.g.  src/mypkg1, src/mypkg2)
136 layouts and try to guess the correct values for the :ref:`packages <declarative
141    configuration for ``packages`` and ``py_modules``.
153 all modules and packages meant for distribution are placed inside this
169 also less error-prone for testing or when using :pep:`420`-style packages.
207    multiple top-level packages or modules.
237 (e.g., you want to *include* in the distribution top-level packages with
239 *exclude* nested packages that would be otherwise included), you can use
247         packages = find:
249         packages = find_namespace:
264         [tool.setuptools.packages]
270 Finding simple packages
274 then return a list of ``str`` representing the packages it could find. To use
290 To have setuptools to automatically include packages found
298         packages = find:
302         [options.packages.find]
317             packages=find_packages(
336         [tool.setuptools.packages.find]
343         When using ``tool.setuptools.packages.find`` in ``pyproject.toml``,
363 .. _Namespace Packages:
365 Finding namespace packages
371 :pep:`namespace packages <420>` are. Here is a quick recap.
373 When you have two packages organized as follows:
389 as if there is only one ``timmins`` on your system. The two packages can then
413         packages = find_namespace:
415         [options.packages.find]
431             packages=find_namespace_packages(where='src'),
445         [tool.setuptools.packages.find]
448     When using ``tool.setuptools.packages.find`` in ``pyproject.toml``,
495 Legacy Namespace Packages
500 to create namespace packages. One is the ``pkg_resources`` style supported by
503 fact they still linger in many existing packages. These two differ in many
505 user guide <https://packaging.python.org/guides/packaging-namespace-packages/>`_
549 Repeat the same for other packages and you can achieve the same result as