forked from Backblaze/B2_Command_Line_Tool
-
Notifications
You must be signed in to change notification settings - Fork 0
/
setup.py
155 lines (127 loc) · 5.7 KB
/
setup.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
######################################################################
#
# File: setup.py
#
# Copyright 2018 Backblaze Inc. All Rights Reserved.
#
# License https://www.backblaze.com/using_b2_code.html
#
######################################################################
"""A setuptools based setup module.
See:
https://packaging.python.org/en/latest/distributing.html
https://github.com/pypa/sampleproject
"""
import platform
import sys
# Always prefer setuptools over distutils
from setuptools import setup, find_packages, __version__ as setuptoolsversion
# To use a consistent encoding
from codecs import open
from os import path
#require at least setuptools 20.2 for PEP 508 conditional dependency support
MIN_SETUPTOOLS_VERSION = (20, 2)
if tuple(int(x) for x in setuptoolsversion.split('.')[:2]) < MIN_SETUPTOOLS_VERSION:
sys.exit(
'setuptools %s.%s or later is required. To fix, try running: pip install "setuptools>=%s.%s"'
% (MIN_SETUPTOOLS_VERSION * 2)
)
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()
with open('requirements.txt', encoding='utf-8') as f:
requirements = f.read().splitlines()
# Jython cannot handle extremely large blocks of code.
# requests 2.12.x that we rely on, relied on idna, which until 2.2.0 contained such block.
# https://github.com/kennethreitz/requests/issues/3711#issuecomment-268522266
if platform.system().lower().startswith('java'):
requirements.append('idna>=2.2.0')
with open('requirements-test.txt', encoding='utf-8') as f:
requirements_test = f.read().splitlines()
with open('requirements-setup.txt', encoding='utf-8') as f:
requirements_setup = f.read().splitlines()
setup(
name='b2',
# 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='1.3.9',
description='Command Line Tool for Backblaze B2',
long_description=long_description,
long_description_content_type='text/markdown',
# The project's main homepage.
url='https://github.com/Backblaze/B2_Command_Line_Tool',
# Author details
author='Backblaze, Inc.',
author_email='support@backblaze.com',
# Choose your license
license='MIT',
# 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 :: 5 - Production/Stable',
# Indicate who your project is intended for
# ??? What are the right classifiers for a command-line tool? ???
'Intended Audience :: Developers',
'Topic :: Software Development :: Libraries',
# 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',
'Programming Language :: Python :: 2.6',
'Programming Language :: Python :: 2.7',
'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3.4',
'Programming Language :: Python :: 3.5',
'Programming Language :: Python :: 3.6',
],
# What does your project relate to?
keywords='backblaze b2 cloud storage',
# You can just specify the packages manually here if your project is
# simple. Or you can use find_packages().
packages=find_packages(exclude=['*contrib*', '*docs*', '*test*']),
# 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
dependency_links=['git+https://github.com/Backblaze/b2-sdk-python#egg=b2sdk'],
install_requires=requirements,
# requirements for tests
tests_require=requirements_test,
# putting nose in test_requires caused a chicken/egg problem
# but apparently setup_requires is broken on most python versions
# setup_requires=requirements_setup,
# 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': [],
'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={'b2': ['requirements.txt', 'requirements-test.txt', 'requirements-setup.txt']},
# 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': ['b2=b2.console_tool:main',],
},
)