|
1
|
|
|
#!/usr/bin/env python3 |
|
2
|
|
|
|
|
3
|
|
|
"""DocManager Setup |
|
4
|
|
|
|
|
5
|
|
|
|
|
6
|
|
|
See also: |
|
7
|
|
|
https://packaging.python.org/en/latest/distributing.html |
|
8
|
|
|
https://github.com/pypa/sampleproject |
|
9
|
|
|
""" |
|
10
|
|
|
|
|
11
|
|
|
import sys |
|
12
|
|
|
from os import path, environ |
|
13
|
|
|
# To use a consistent encoding |
|
14
|
|
|
from codecs import open |
|
15
|
|
|
|
|
16
|
|
|
# Always prefer setuptools over distutils |
|
17
|
|
|
from setuptools import setup, find_packages |
|
18
|
|
|
from setuptools.command.test import test as TestCommand |
|
19
|
|
|
|
|
20
|
|
|
|
|
21
|
|
|
here = path.abspath(path.dirname(__file__)) |
|
22
|
|
|
|
|
23
|
|
|
|
|
24
|
|
|
setupdict = dict( |
|
25
|
|
|
name='docmanager', |
|
26
|
|
|
|
|
27
|
|
|
# Versions should comply with PEP440. For a discussion on single-sourcing |
|
28
|
|
|
# the version across setup.py and the project code, see |
|
29
|
|
|
# https://packaging.python.org/en/latest/single_source_version.html |
|
30
|
|
|
version='3.3.4', |
|
31
|
|
|
|
|
32
|
|
|
description='Manage Meta Information in DocBook5-XML Files', |
|
33
|
|
|
# long_description=long_description, |
|
34
|
|
|
|
|
35
|
|
|
# The project's main homepage. |
|
36
|
|
|
url='https://github.com/openSUSE/docmanager', |
|
37
|
|
|
|
|
38
|
|
|
# Author details |
|
39
|
|
|
author='Rick Salevsky', |
|
40
|
|
|
author_email='[email protected]', |
|
41
|
|
|
|
|
42
|
|
|
# Choose your license |
|
43
|
|
|
license='GPL-3.0', |
|
44
|
|
|
|
|
45
|
|
|
# See https://pypi.python.org/pypi?%3Aaction=list_classifiers |
|
46
|
|
|
classifiers=[ |
|
47
|
|
|
# How mature is this project? Common values are |
|
48
|
|
|
# 3 - Alpha |
|
49
|
|
|
# 4 - Beta |
|
50
|
|
|
# 5 - Production/Stable |
|
51
|
|
|
'Development Status :: 5 - Production/Stable', |
|
52
|
|
|
|
|
53
|
|
|
# Indicate who your project is intended for |
|
54
|
|
|
'Topic :: Documentation', |
|
55
|
|
|
'Topic :: Software Development :: Documentation', |
|
56
|
|
|
'Intended Audience :: Developers', |
|
57
|
|
|
|
|
58
|
|
|
# Pick your license as you wish (should match "license" above) |
|
59
|
|
|
'License :: OSI Approved :: GNU General Public License v3 (GPLv3)', |
|
60
|
|
|
'License :: OSI Approved :: GNU General Public License v2 (GPLv2)', |
|
61
|
|
|
|
|
62
|
|
|
# Supported Python versions |
|
63
|
|
|
'Programming Language :: Python :: 3.3', |
|
64
|
|
|
'Programming Language :: Python :: 3.4', |
|
65
|
|
|
], |
|
66
|
|
|
|
|
67
|
|
|
# What does your project relate to? |
|
68
|
|
|
keywords='docbook5 metainformation', |
|
69
|
|
|
|
|
70
|
|
|
# Includes data files from MANIFEST.in |
|
71
|
|
|
# |
|
72
|
|
|
# See also: |
|
73
|
|
|
# http://stackoverflow.com/a/16576850 |
|
74
|
|
|
# https://pythonhosted.org/setuptools/setuptools.html#including-data-files |
|
75
|
|
|
include_package_data = True, |
|
76
|
|
|
|
|
77
|
|
|
# You can just specify the packages manually here if your project is |
|
78
|
|
|
# simple. Or you can use find_packages(). |
|
79
|
|
|
packages=find_packages('src'), |
|
80
|
|
|
package_dir={'': 'src'}, |
|
81
|
|
|
|
|
82
|
|
|
# List run-time dependencies here. These will be installed by pip when |
|
83
|
|
|
# your project is installed. For an analysis of "install_requires" vs pip's |
|
84
|
|
|
# requirements files see: |
|
85
|
|
|
# https://packaging.python.org/en/latest/requirements.html |
|
86
|
|
|
install_requires=['lxml'], |
|
87
|
|
|
|
|
88
|
|
|
# List additional groups of dependencies here (e.g. development |
|
89
|
|
|
# dependencies). You can install these using the following syntax, |
|
90
|
|
|
# for example: |
|
91
|
|
|
# $ pip install -e .[dev,test] |
|
92
|
|
|
#extras_require={ |
|
93
|
|
|
# 'dev': ['check-manifest'], |
|
94
|
|
|
# 'test': ['coverage'], |
|
95
|
|
|
#}, |
|
96
|
|
|
|
|
97
|
|
|
# If there are data files included in your packages that need to be |
|
98
|
|
|
# installed, specify them here. If using Python 2.6 or less, then these |
|
99
|
|
|
# have to be included in MANIFEST.in as well. |
|
100
|
|
|
package_data={ |
|
101
|
|
|
'docmanager': ['template/*'], |
|
102
|
|
|
}, |
|
103
|
|
|
|
|
104
|
|
|
# Although 'package_data' is the preferred approach, in some case you may |
|
105
|
|
|
# need to place data files outside of your packages. See: |
|
106
|
|
|
# http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa |
|
107
|
|
|
# In this case, 'data_file' will be installed into '<sys.prefix>/my_data' |
|
108
|
|
|
# data_files=[('my_data', ['data/data_file'])], |
|
109
|
|
|
|
|
110
|
|
|
# To provide executable scripts, use entry points in preference to the |
|
111
|
|
|
# "scripts" keyword. Entry points provide cross-platform support and allow |
|
112
|
|
|
# pip to create the appropriate form of executable for the target platform. |
|
113
|
|
|
entry_points={ |
|
114
|
|
|
'console_scripts': [ |
|
115
|
|
|
'docmanager=docmanager:main', |
|
116
|
|
|
], |
|
117
|
|
|
}, |
|
118
|
|
|
|
|
119
|
|
|
# Required packages for testing |
|
120
|
|
|
setup_requires=['pytest-runner',], |
|
121
|
|
|
tests_require=['pytest', 'pytest-cov', ], |
|
122
|
|
|
# |
|
123
|
|
|
) |
|
124
|
|
|
|
|
125
|
|
|
# Call it: |
|
126
|
|
|
setup(**setupdict) |
|
127
|
|
|
|
openSUSE /
docmanager
