Skip to content
This repository has been archived by the owner on Feb 26, 2018. It is now read-only.
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time
"""gdistcc: the easy way to compile in the cloud!
import pypandoc
# Always prefer setuptools over distutils
from setuptools import setup, find_packages
# To use a consistent encoding
from codecs import open
from os import path
here = path.abspath(path.dirname(__file__))
# Versions should comply with PEP440. For a discussion on single-sourcing
# the version across and the project code, see
description='gdistcc: the easy way to compile in the cloud!',
long_description=pypandoc.convert('', 'rst'),
# The project's main homepage.
# Author details
author='Andrew Peabody',
# Choose your license
# See
# How mature is this project? Common values are
# 3 - Alpha
# 4 - Beta
# 5 - Production/Stable
'Development Status :: 3 - Alpha',
# Indicate who your project is intended for
'Intended Audience :: Developers',
'Topic :: Software Development :: Build Tools',
# Pick your license as you wish (should match "license" above)
'License :: OSI Approved :: Apache Software License',
# Specify the Python versions you support here. In particular, ensure
# that you indicate whether you support Python 2, Python 3 or both.
'Programming Language :: Python :: 2',
'Programming Language :: Python :: 2.7',
'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3.5',
# What does your project relate to?
keywords='google compute engine distcc make',
# You can just specify the packages manually here if your project is
# simple. Or you can use find_packages().
packages=['gdistcc', 'gdistcc.startup-scripts'],
# Alternatively, if you want to distribute just a, uncomment
# this:
# py_modules=["gdistcc"],
# List run-time dependencies here. These will be installed by pip when
# your project is installed. For an analysis of "install_requires" vs pip's
# requirements files see:
install_requires=['google-api-python-client', 'six'],
# List additional groups of dependencies here (e.g. development
# dependencies). You can install these using the following syntax,
# for example:
# $ pip install -e .[dev,test]
# If there are data files included in your packages that need to be
# installed, specify them here. If using Python 2.6 or less, then these
# have to be included in as well.
'gdistcc': ['settings.json'],
'gdistcc.startup-scripts': ['*.sh']
# Although 'package_data' is the preferred approach, in some case you may
# need to place data files outside of your packages. See:
# # noqa
# In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
# data_files=[('my_data', ['data/data_file'])],
# To provide executable scripts, use entry points in preference to the
# "scripts" keyword. Entry points provide cross-platform support and allow
# pip to create the appropriate form of executable for the target platform.
'console_scripts': [