Statistics
| Branch: | Tag: | Revision:

hlrc / client / python / setup.py @ 0c286af0

History | View | Annotate | Download (3.862 KB)

1
"""[h]igh [l]evel [r]obot [c]ontrol client project
2

3

4
See:
5
http://opensource.cit-ec.uni-bielefeld.de/hlrc
6
"""
7

    
8
# Always prefer setuptools over distutils
9
from setuptools import setup, find_packages
10
# To use a consistent encoding
11
from codecs import open
12
from os import path
13

    
14
here = path.abspath(path.dirname(__file__))
15

    
16
# Get the long description from the relevant file
17
with open(path.join(here, 'DESCRIPTION.rst'), encoding='utf-8') as f:
18
    long_description = f.read()
19

    
20
setup(
21
    name='hlrc_client',
22

    
23
    # Versions should comply with PEP440.  For a discussion on single-sourcing
24
    # the version across setup.py and the project code, see
25
    # https://packaging.python.org/en/latest/single_source_version.html
26
    version='1.2.0',
27

    
28
    description='[h]igh [l]evel [r]obot [c]ontrol client project',
29
    long_description=long_description,
30

    
31
    # The project's main homepage.
32
    url='http://opensource.cit-ec.uni-bielefeld.de/hlrc',
33

    
34
    # Author details
35
    author='Simon Schulz',
36
    author_email='sschulz@techfak.uni-bielefeld.de',
37

    
38
    # Choose your license
39
    license='GPLv3',
40

    
41
    # See https://pypi.python.org/pypi?%3Aaction=list_classifiers
42
    classifiers=[
43
        # How mature is this project? Common values are
44
        #   3 - Alpha
45
        #   4 - Beta
46
        #   5 - Production/Stable
47
        'Development Status :: 3 - Alpha',
48

    
49
        # Indicate who your project is intended for
50
        'Intended Audience :: Developers',
51
        'Topic :: Scientific/Engineering',
52

    
53
        # Pick your license as you wish (should match "license" above)
54
        'License :: OSI Approved :: GNU General Public License v3 (GPLv3)',
55

    
56
        # Specify the Python versions you support here. In particular, ensure
57
        # that you indicate whether you support Python 2, Python 3 or both.
58
        'Programming Language :: Python :: 2',
59
        'Programming Language :: Python :: 2.6',
60
        'Programming Language :: Python :: 2.7',
61
        'Programming Language :: Python :: 3',
62
        'Programming Language :: Python :: 3.2',
63
        'Programming Language :: Python :: 3.3',
64
        'Programming Language :: Python :: 3.4',
65
    ],
66

    
67
    # What does your project relate to?
68
    keywords='sample setuptools development',
69

    
70
    # You can just specify the packages manually here if your project is
71
    # simple. Or you can use find_packages().
72
    packages=find_packages(exclude=['contrib', 'docs', 'tests*']),
73

    
74
    # List run-time dependencies here.  These will be installed by pip when
75
    # your project is installed. For an analysis of "install_requires" vs pip's
76
    # requirements files see:
77
    # https://packaging.python.org/en/latest/requirements.html
78
    install_requires=['peppercorn'],
79

    
80
    # List additional groups of dependencies here (e.g. development
81
    # dependencies). You can install these using the following syntax,
82
    # for example:
83
    # $ pip install -e .[dev,test]
84
    extras_require={
85
        'dev': ['check-manifest'],
86
        'test': ['coverage'],
87
    },
88

    
89
    # If there are data files included in your packages that need to be
90
    # installed, specify them here.  If using Python 2.6 or less, then these
91
    # have to be included in MANIFEST.in as well.
92
    package_data={
93
        #'sample': ['package_data.dat'],
94
    },
95

    
96
    # Although 'package_data' is the preferred approach, in some case you may
97
    # need to place data files outside of your packages. See:
98
    # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
99
    # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
100
    data_files=[], #('my_data', ['data/data_file'])],
101

    
102
    # To provide executable scripts, use entry points in preference to the
103
    # "scripts" keyword. Entry points provide cross-platform support and allow
104
    # pip to create the appropriate form of executable for the target platform.
105
    entry_points={
106
        'console_scripts': [
107
            #'sample=sample:main',
108
        ],
109
    },
110
)