|
1 | 1 | """Setup file for distribution artifacts."""
|
| 2 | +from __future__ import print_function |
| 3 | + |
2 | 4 | from os import path
|
3 |
| -from setuptools import setup, find_packages |
| 5 | +import sys |
| 6 | + |
| 7 | +from setuptools import find_packages |
| 8 | +from setuptools import setup |
| 9 | + |
| 10 | +import firebase_admin |
| 11 | + |
4 | 12 |
|
| 13 | +if sys.version_info < (2, 7): |
| 14 | + print('firebase_admin requires python2 version >= 2.7 or python3.', file=sys.stderr) |
| 15 | + sys.exit(1) |
5 | 16 |
|
6 |
| -here = path.abspath(path.dirname(__file__)) |
7 | 17 |
|
8 | 18 | long_description = ('The Firebase Admin Python SDK enables server-side (backend) Python developers '
|
9 | 19 | 'to integrate Firebase into their services and applications.')
|
| 20 | +install_requires = [ |
| 21 | + 'oauth2client>=4.0.0', |
| 22 | + 'six>=1.6.1' |
| 23 | +] |
| 24 | + |
| 25 | +version = firebase_admin.__version__ |
10 | 26 |
|
11 | 27 | setup(
|
12 | 28 | name='firebase_admin',
|
13 |
| - |
14 |
| - # Versions should comply with PEP440. For a discussion on single-sourcing |
15 |
| - # the version across setup.py and the project code, see |
16 |
| - # https://packaging.python.org/en/latest/single_source_version.html |
17 |
| - version='0.0.1', |
18 |
| - |
| 29 | + version=version, |
19 | 30 | description='Firebase Admin Python SDK',
|
20 | 31 | long_description=long_description,
|
21 |
| - |
22 | 32 | url='https://firebase.google.com/docs/admin/setup/',
|
23 |
| - |
24 |
| - # Author details |
25 | 33 | author='Firebase',
|
26 |
| - |
27 |
| - # Choose your license |
28 | 34 | license='https://firebase.google.com/terms/',
|
29 |
| - |
30 |
| - # See https://pypi.python.org/pypi?%3Aaction=list_classifiers |
| 35 | + keywords='firebase cloud development', |
| 36 | + install_requires=install_requires, |
| 37 | + packages=find_packages(exclude=['tests']), |
31 | 38 | classifiers=[
|
32 |
| - # How mature is this project? Common values are |
33 |
| - # 3 - Alpha |
34 |
| - # 4 - Beta |
35 |
| - # 5 - Production/Stable |
36 | 39 | 'Development Status :: 3 - Alpha',
|
37 |
| - |
38 |
| - # Indicate who your project is intended for |
39 | 40 | 'Intended Audience :: Developers',
|
40 | 41 | 'Topic :: Software Development :: Build Tools',
|
41 |
| - |
42 |
| - # Specify the Python versions you support here. In particular, ensure |
43 |
| - # that you indicate whether you support Python 2, Python 3 or both. |
44 | 42 | 'Programming Language :: Python :: 2',
|
45 | 43 | 'Programming Language :: Python :: 2.7',
|
| 44 | + 'Programming Language :: Python :: 3', |
| 45 | + 'Programming Language :: Python :: 3.3', |
| 46 | + 'Programming Language :: Python :: 3.5', |
46 | 47 | ],
|
47 |
| - |
48 |
| - # What does your project relate to? |
49 |
| - keywords='firebase cloud development', |
50 |
| - |
51 |
| - packages=find_packages(exclude=['tests']), |
52 |
| - |
53 |
| - # List run-time dependencies here. These will be installed by pip when |
54 |
| - # your project is installed. For an analysis of "install_requires" vs pip's |
55 |
| - # requirements files see: |
56 |
| - # https://packaging.python.org/en/latest/requirements.html |
57 |
| - install_requires=[ |
58 |
| - 'oauth2client>=4.0.0', |
59 |
| - 'six>=1.6.1' |
60 |
| - ], |
61 |
| - |
62 |
| - # List additional groups of dependencies here (e.g. development |
63 |
| - # dependencies). You can install these using the following syntax, |
64 |
| - # for example: |
65 |
| - # $ pip install -e .[dev,test] |
66 |
| - #extras_require={ |
67 |
| - # 'dev': ['check-manifest'], |
68 |
| - # 'test': ['coverage'], |
69 |
| - #}, |
70 |
| - |
71 |
| - # If there are data files included in your packages that need to be |
72 |
| - # installed, specify them here. If using Python 2.6 or less, then these |
73 |
| - # have to be included in MANIFEST.in as well. |
74 |
| - #package_data={ |
75 |
| - # 'sample': ['package_data.dat'], |
76 |
| - #}, |
77 |
| - |
78 |
| - # Although 'package_data' is the preferred approach, in some case you may |
79 |
| - # need to place data files outside of your packages. See: |
80 |
| - # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa |
81 |
| - # In this case, 'data_file' will be installed into '<sys.prefix>/my_data' |
82 |
| - #data_files=[('my_data', ['data/data_file'])], |
83 |
| - |
84 |
| - # To provide executable scripts, use entry points in preference to the |
85 |
| - # "scripts" keyword. Entry points provide cross-platform support and allow |
86 |
| - # pip to create the appropriate form of executable for the target platform. |
87 |
| - #entry_points={ |
88 |
| - # 'console_scripts': [ |
89 |
| - # 'sample=sample:main', |
90 |
| - # ], |
91 |
| - #}, |
92 | 48 | )
|
0 commit comments