python-setuptools-git
Port variant py310
Summary Revision control system plugin for Git (3.10)
Package version 1.2
Homepage No known homepage
Keywords python
Maintainer Python Automaton
License Not yet specified
Other variants py39
Ravenports Buildsheet | History
Ravensource Port Directory | History
Last modified 20 NOV 2021, 04:14:38 UTC
Port created 20 APR 2020, 15:00:59 UTC
Subpackage Descriptions
single About ----- This is a plugin for setuptools that enables git integration. Once installed, Setuptools can be told to include in a package distribution all the files tracked by git. This is an alternative to explicit inclusion specifications with ``MANIFEST.in``. A package distribution here refers to a package that you create using setup.py, for example:: $> python setup.py sdist $> python setup.py bdist_rpm $> python setup.py bdist_egg This package was formerly known as gitlsfiles. The name change is the result of an effort by the setuptools plugin developers to provide a uniform naming convention. Installation ------------ With easy_install:: $> easy_install setuptools_git Alternative manual installation:: $> tar -zxvf setuptools_git-X.Y.Z.tar.gz $> cd setuptools_git-X.Y.Z $> python setup.py install Where X.Y.Z is a version number. Usage ----- To activate this plugin, you must first package your python module with ``setup.py`` and use setuptools. The former is well documented in the [distutils manual]. To use setuptools instead of distutils, just edit ``setup.py`` and change: .. code-block:: python from distutils.core import setup to: .. code-block:: python from setuptools import setup, find_packages When Setuptools builds a source package, it always includes all files tracked by your revision control system, if it knows how to learn what those files are. When Setuptools builds a binary package, you can ask it to include all files tracked by your revision control system, by adding these argument to your invocation of `setup()`: .. code-block:: python setup(..., packages=find_packages(), include_package_data=True, ...) which will detect that a directory is a package if it contains a ``__init__.py`` file. Alternatively, you can do without ``__init__.py`` files and tell Setuptools explicitly which packages to process: .. code-block:: python setup(..., packages=["a_package", "another_one"], include_package_data=True, ...) This plugin lets setuptools know what files are tracked by your git revision control tool. Setuptools ships with support for cvs and subversion. Other plugins like this one are available for bzr, darcs, monotone, mercurial, and many others. It might happen that you track files with your revision control system that you don't want to include in your packages. In that case, you can prevent setuptools from packaging those files with a directive in your ``MANIFEST.in``, for example:: exclude .gitignore recursive-exclude images *.xcf *.blend In this example, we prevent setuptools from packaging ``.gitignore and the Gimp and Blender source files found under the images`` directory. Files to exclude from the package can also be listed in the `setup()` directive. To do the same as the MANIFEST.in above, do: .. code-block:: python
Configuration Switches (platform-specific settings discarded)
PY310 ON Build using Python 3.10 PY39 OFF Build using Python 3.9
Package Dependencies by Type
Build (only) python-pip:single:py310
autoselect-python:single:standard
Build and Runtime python310:single:standard
Download groups
main mirror://PYPIWHL/05/97/dd99fa9c0d9627a7b3c103a00f1566d8193aca8d473884ed258cca82b06f
Distribution File Information
e7764dccce7d97b4b5a330d7b966aac6f9ac026385743fd6cedad553f2494cfa 10965 setuptools_git-1.2-py2.py3-none-any.whl
Ports that require python-setuptools-git:py310
python-ioflo:py310 Flow Programming Automated Reasoning Engine (3.10)
python-raet:py310 Reliable Asynchronous Event Transport (3.10)