Lines Matching +full:some +full:- +full:project +full:- +full:name

8 a distutils extension as a separate project, and then have projects that need
15 Services and Plugins` above for some more background on entry points.)
19 ---------------
24 project's setup script::
38 Once a project containing such entry points has been activated on ``sys.path``,
39 (e.g. by running "install" or "develop" with a site-packages installation
40 directory) the command(s) will be available to any ``setuptools``-based setup
41 scripts.  It is not necessary to use the ``--command-packages`` option or
45 how setuptools' own commands are installed: the setuptools project's setup
57 ----------------------------
67 distutils extension project's setup script::
85 a non-None value.  Here's an example validation function::
95 the attribute name, and the attribute value.  It should raise a
97 is invalid.  Remember, your function will only be called with non-None values,
110 script using your extension lists your project in its ``setup_requires``
115 --------------------------------
118 suit the purposes of that project. For example, a tool that infers the
119 ``Distribution.version`` from SCM-metadata may need to hook into the
133 .. _Adding new EGG-INFO Files:
135 Adding new EGG-INFO Files
136 -------------------------
138 Some extensible applications or frameworks may want to allow third parties to
139 develop plugins with application or framework-specific metadata included in
140 the plugins' EGG-INFO directory, for easy access via the ``pkg_resources``
143 that defines a new setup keyword, and then uses that data to write an EGG-INFO
149 lines that will be written to ``foo_bar.txt`` in the EGG-INFO directory of any
150 project that uses the argument::
192 -------------------------------------------------
197 - Git and Mercurial: :pypi:`setuptools_scm`
198 - SVN: :pypi:`setuptools_svn`
203 accepting a single directory name, and should yield all the filenames within
210 .. code-block:: python
238   passed-in directory name.  Absolute paths are NOT allowed, nor are relative
239   paths that reference a parent directory of the passed-in directory.
241 * Your finder function MUST accept an empty string as the directory name,
243   yield relative paths.  So, yielding a subdirectory named ``some/dir`` under
244   the current directory should NOT be rendered as ``./some/dir`` or
245   ``/somewhere/some/dir``, but *always* as simply ``some/dir``