This repository has been archived by the owner. It is now read-only.
Permalink
Browse files

inital commit for PyPI setup

  • Loading branch information...
apeabody committed Jun 19, 2016
1 parent fde1159 commit 9e3df53357f4a56f2cc396f36b5d8fefea5dbc91
Showing with 114 additions and 0 deletions.
  1. +1 −0 .travis.yml
  2. +2 −0 requirements.txt
  3. +5 −0 setup.cfg
  4. +106 −0 setup.py
View
@@ -1,6 +1,7 @@
language: python
python:
- "2.7"
- "3.5"
# command to install dependencies
# install: "pip install -r google-api-python-client"
# # command to run tests
View
@@ -1,2 +1,4 @@
six
oauth2client
google-api-python-client
codeclimate-test-reporter
View
@@ -0,0 +1,5 @@
[bdist_wheel]
# This flag says that the code is written to work on both Python 2 and Python
# 3. If at all possible, it is good practice to do this. If you cannot, you
# will need to generate wheels for each Python version that you support.
universal=1
View
106 setup.py
@@ -0,0 +1,106 @@
"""gdistcc: the easy way to compile in the cloud!
See:
https://github.com/apeabody/gdistcc
"""
# 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__))
# Get the long description from the README file
with open(path.join(here, 'README.md'), encoding='utf-8') as f:
long_description = f.read()
setup(
name='gdistcc',
# Versions should comply with PEP440. For a discussion on single-sourcing
# the version across setup.py and the project code, see
# https://packaging.python.org/en/latest/single_source_version.html
version='0.9',
description='gdistcc: the easy way to compile in the cloud!',
long_description=long_description,
# The project's main homepage.
url='https://github.com/apeabody/gdistcc',
# Author details
author='Andrew Peabody',
author_email='apeabody@gmail.com',
# Choose your license
license='APACHE',
# See https://pypi.python.org/pypi?%3Aaction=list_classifiers
classifiers=[
# How mature is this project? Common values are
# 3 - Alpha
# 4 - Beta
# 5 - Production/Stable
'Development Status :: 4 - Beta',
# 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 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=find_packages(exclude=['utils']),
# Alternatively, if you want to distribute just a my_module.py, uncomment
# this:
# py_modules=["my_module"],
# 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:
# https://packaging.python.org/en/latest/requirements.html
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 MANIFEST.in as well.
# package_data={
# 'sample': ['package_data.dat'],
# },
# Although 'package_data' is the preferred approach, in some case you may
# need to place data files outside of your packages. See:
# http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # 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.
# entry_points={
# 'console_scripts': [
# 'sample=sample:main',
# ],
# },
)

0 comments on commit 9e3df53

Please sign in to comment.