hlrc / tts_bridge / mary / setup.py @ 84534fbf
History | View | Annotate | Download (4.125 KB)
1 | 0c15613f | Simon Schulz | """[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='mary_tts_bridge',
|
||
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='0.1',
|
||
27 | |||
28 | description='mary tts provider bridge',
|
||
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 | e21d7f2c | Simon Schulz | #include package data?
|
42 | include_package_data = True,
|
||
43 | |||
44 | 0c15613f | Simon Schulz | # See https://pypi.python.org/pypi?%3Aaction=list_classifiers
|
45 | classifiers=[ |
||
46 | # How mature is this project? Common values are
|
||
47 | # 3 - Alpha
|
||
48 | # 4 - Beta
|
||
49 | # 5 - Production/Stable
|
||
50 | 'Development Status :: 3 - Alpha',
|
||
51 | |||
52 | # Indicate who your project is intended for
|
||
53 | 'Intended Audience :: Developers',
|
||
54 | 'Topic :: Scientific/Engineering',
|
||
55 | |||
56 | # Pick your license as you wish (should match "license" above)
|
||
57 | 'License :: OSI Approved :: GNU General Public License v3 (GPLv3)',
|
||
58 | |||
59 | # Specify the Python versions you support here. In particular, ensure
|
||
60 | # that you indicate whether you support Python 2, Python 3 or both.
|
||
61 | 'Programming Language :: Python :: 2',
|
||
62 | 'Programming Language :: Python :: 2.6',
|
||
63 | 'Programming Language :: Python :: 2.7',
|
||
64 | 'Programming Language :: Python :: 3',
|
||
65 | 'Programming Language :: Python :: 3.2',
|
||
66 | 'Programming Language :: Python :: 3.3',
|
||
67 | 'Programming Language :: Python :: 3.4',
|
||
68 | e34ce888 | Birte Richter | 'Programming Language :: Python :: 3.8',
|
69 | 0c15613f | Simon Schulz | ], |
70 | |||
71 | # What does your project relate to?
|
||
72 | keywords='sample setuptools development',
|
||
73 | |||
74 | # You can just specify the packages manually here if your project is
|
||
75 | # simple. Or you can use find_packages().
|
||
76 | packages=find_packages(exclude=['contrib', 'docs', 'tests*']), |
||
77 | |||
78 | # List run-time dependencies here. These will be installed by pip when
|
||
79 | # your project is installed. For an analysis of "install_requires" vs pip's
|
||
80 | # requirements files see:
|
||
81 | # https://packaging.python.org/en/latest/requirements.html
|
||
82 | install_requires=[], |
||
83 | |||
84 | # List additional groups of dependencies here (e.g. development
|
||
85 | # dependencies). You can install these using the following syntax,
|
||
86 | # for example:
|
||
87 | # $ pip install -e .[dev,test]
|
||
88 | extras_require={ |
||
89 | 'dev': ['check-manifest'], |
||
90 | 'test': ['coverage'], |
||
91 | }, |
||
92 | |||
93 | # If there are data files included in your packages that need to be
|
||
94 | # installed, specify them here. If using Python 2.6 or less, then these
|
||
95 | # have to be included in MANIFEST.in as well.
|
||
96 | package_data={ |
||
97 | e21d7f2c | Simon Schulz | '': ['data/connection_failed.*'], |
98 | 0c15613f | Simon Schulz | #'sample': ['package_data.dat'],
|
99 | }, |
||
100 | |||
101 | # Although 'package_data' is the preferred approach, in some case you may
|
||
102 | # need to place data files outside of your packages. See:
|
||
103 | # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
|
||
104 | # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
|
||
105 | data_files=[], #('my_data', ['data/data_file'])],
|
||
106 | |||
107 | #scripts=['bin/hlrc_test_gui.py'],
|
||
108 | a2ff94c0 | flier | # Workaround for: http://bugs.python.org/issue856103
|
109 | 246c4439 | flier | zip_safe=False,
|
110 | 0c15613f | Simon Schulz | |
111 | # To provide executable scripts, use entry points in preference to the
|
||
112 | # "scripts" keyword. Entry points provide cross-platform support and allow
|
||
113 | # pip to create the appropriate form of executable for the target platform.
|
||
114 | entry_points={ |
||
115 | 'console_scripts': [
|
||
116 | 163a7434 | Simon Schulz | 'mary_tts_provider=mary_tts_bridge.MaryTTSBridge:main',
|
117 | 0c15613f | Simon Schulz | ], |
118 | }, |
||
119 | ) |