"""Setup module for xdfile"""

# Always prefer setuptools over distutils

from setuptools import find_packages, setup

# To use a consistent encoding

# from codecs import open

from os import path

package_root = path.abspath(path.dirname(__file__))

# Get the long description from the README file

with open('README.md') as readme:

long_description = readme.read()

with open('VERSION') as version_file:

version = version_file.read().strip()

def requirements():

with open("requirements.txt") as f:

return f.read().split("\n")

setup(

name='xdfile',

# TODO: figure out a spot for a single version string for everything.

# 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=version,

description='A futureproof crossword corpus toolset',

long_description='TODO: fill this out.',

# The project's main homepage.

url='https://github.com/century-arcade/xd',

# Author details

author='Saul Pwanson',

author_email='[email protected]',

# Choose your license

license='MIT',

# Testing

setup_requires=['pytest-runner'],

tests_require=['pytest'],

# 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 :: 3 - Alpha',

# Indicate who your project is intended for

'Intended Audience :: End Users/Desktop',

# 'Topic :: Software Development :: Build Tools',

# Pick your license as you wish (should match "license" above)

'License :: OSI Approved :: MIT 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.7',

],

# What does your project relate to?

keywords='crossword puzzles',

# You can just specify the packages manually here if your project is

# simple. Or you can use find_packages().

packages=find_packages(exclude=['scripts', 'bin']),

# 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=requirements(),

# 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]

extras_require={

'dev': ['check-manifest', 'tox'],

},

# 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',

],

},

)