• Home
  • Raw
  • Download

Lines Matching +full:version +full:- +full:script

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
37 directory.) A minimal setup script to describe this situation would be::
41 version='1.0',
60 and the setup script might be ::
64 version='1.0',
73 .. _pure-pkg:
85 The setup script from the last example could also be written as ::
89 version='1.0',
108 version='1.0',
114 package (or in sub-packages). For example, if the :mod:`foo` and :mod:`bar`
126 requires the least work to describe in your setup script::
130 version='1.0',
145 an appropriate setup script would be ::
149 version='1.0',
163 in which case your setup script would be ::
167 version='1.0',
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::
190 then the corresponding setup script would be ::
194 version='1.0',
199 .. _single-ext:
213 If the :mod:`foo` extension belongs in the root package, the setup script for
219 version='1.0',
231 version='1.0',
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
244 Let's take an example with a simple script::
252 .. code-block:: shell-session
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::
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
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`,
308 where ``NAME`` is the name of the project, ``VERSION`` its version as defined
309 in the Metadata, and ``pyX.X`` the major and minor version of Python like
318 >>> metadata.read_pkg_file(open('distribute-0.6.8-py2.7.egg-info'))
321 >>> metadata.version
329 >>> pkg_info_path = 'distribute-0.6.8-py2.7.egg-info'
335 .. % \label{multiple-ext}