Lines Matching +full:- +full:- +full:setup

20 .. _pure-mod:
27 ``py_modules`` option in the setup script.
29 In the simplest case, you'll have two files to worry about: a setup script and
33            setup.py
37 directory.)  A minimal setup script to describe this situation would be::
39    from distutils.core import setup
40    setup(name='foo',
53 setup might look like this::
56            setup.py
60 and the setup script might be  ::
62    from distutils.core import setup
63    setup(name='foobar',
73 .. _pure-pkg:
85 The setup script from the last example could also be written as  ::
87    from distutils.core import setup
88    setup(name='foobar',
99            setup.py
106    from distutils.core import setup
107    setup(name='foobar',
114 package (or in sub-packages).  For example, if the :mod:`foo`  and :mod:`bar`
119            setup.py
126 requires the least work to describe in your setup script::
128    from distutils.core import setup
129    setup(name='foobar',
139            setup.py
145 an appropriate setup script would be  ::
147    from distutils.core import setup
148    setup(name='foobar',
158            setup.py
163 in which case your setup script would be  ::
165    from distutils.core import setup
166    setup(name='foobar',
174 If you have sub-packages, they must be explicitly listed in ``packages``,
175 but any entries in ``package_dir`` automatically extend to sub-packages.
178 :file:`__init__.py` files.)  Thus, if the default layout grows a sub-package::
181            setup.py
190 then the corresponding setup script would be  ::
192    from distutils.core import setup
193    setup(name='foobar',
199 .. _single-ext:
210            setup.py
213 If the :mod:`foo` extension belongs in the root package, the setup script for
216    from distutils.core import setup
218    setup(name='foobar',
228    from distutils.core import setup
230    setup(name='foobar',
238 The ``check`` command allows you to verify if your package meta-data
241 To run it, just call it using your :file:`setup.py` script. If something is
246     from distutils.core import setup
248     setup(name='foobar')
252 .. code-block:: shell-session
254     $ python setup.py check
256     warning: check: missing required meta-data: version, url
257     warning: check: missing meta-data: either (author and author_email) or
265 For example, if the :file:`setup.py` script is changed like this::
267     from distutils.core import setup
276     setup(name='foobar', version='1', author='tarek',
283 .. code-block:: shell-session
285     $ python setup.py check --restructuredtext
293 The :func:`distutils.core.setup` function provides a command-line interface
295 ``setup.py`` script of a given project:
297 .. code-block:: shell-session
299     $ python setup.py --name
303 :func:`distutils.core.setup`  function. Although, when a source or binary
305 in a static file called :file:`PKG-INFO`. When a Distutils-based project is
306 installed in Python, the :file:`PKG-INFO` file is copied alongside the modules
307 and packages of the distribution under :file:`NAME-VERSION-pyX.X.egg-info`,
318     >>> metadata.read_pkg_file(open('distribute-0.6.8-py2.7.egg-info'))
329     >>> pkg_info_path = 'distribute-0.6.8-py2.7.egg-info'
335 .. % \label{multiple-ext}