Lines Matching +full:build +full:- +full:packages

2 Building and Distributing Packages with Setuptools
6 that allow developers to more easily build and
7 distribute Python packages, especially ones that have dependencies on other
8 packages.
10 Packages built and distributed using ``setuptools`` look to the user like
11 ordinary Python packages based on the ``distutils``.
15 * Create `Python Eggs <http://peak.telecommunity.com/DevCenter/PythonEggs>`_ -
16   a single-file importable distribution format
18 * Enhanced support for accessing data files hosted in zipped packages.
20 * Automatically include all packages in your source tree, without listing them
33   still work even when the end-user doesn't have Cython installed (as long as
34   you include the Cython-generated C in your source distribution)
36 * Command aliases - create project-specific, per-user, or site-wide shortcut
51 -----------------
53 -----------------
93 packages during the initialization of the ``pkg_resources`` runtime, and also
95 packages work at all.  In some future releases, you'll be responsible
103 Namespace packages without declaration lines will not work
124 setup.cfg-only projects
130 build is invoked, ``setuptools`` emulates a dummy ``setup.py`` file containing
136     incompatible with ``pip install -e .``.
138 This means that you can have a Python project with all build configuration
145 * Specify build requirements and :pep:`517` build backend in
149   .. code-block:: toml
151       [build-system]
156       build-backend = "setuptools.build_meta"
158 * Use a :pep:`517` compatible build frontend, such as ``pip >= 19`` or ``build``.
177 .. code-block:: python
217 ----
221    Python packages, or packages with simple C extensions (that don't require
228 .. _MANIFEST.in: https://packaging.python.org/en/latest/guides/using-manifest-in/